List audit events
What changed, who or which agent changed it, and through which surface, for configuration and money-affecting actions: outcome definition, plan and webhook endpoint changes, provider and routing changes, reversals, dispute decisions, credit grants and voids, config proposals, holding a catalog price change (catalog.price_change_held) and a customer’s auto top-up rule being created, changed or turned off (auto_top_up.created, auto_top_up.updated, auto_top_up.turned_off), each with its actor. Events are kept for at least 13 months. Needs audit:read.
Authentication
A secret key (rl_sk_test_..., rl_sk_live_...) or a restricted key with limited scopes (rl_rk_test_..., rl_rk_live_...). A restricted key can carry agent: true and an expires_at, and is what a coding agent should hold. Keys end in a checksum so secret scanners can recognize them. People create, roll and revoke keys in the dashboard; GET /v1/api_keys lists them, masked.
Query parameters
The next_cursor from the previous page.