Retrieve an outcome charge
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.
Path parameters
The outcome charge ID (oc_...).
Response
pending: inside the confirmation window and not billed. disputed: a dispute is open. confirmed: billed, and reversible until reversible_until. locked: final. reversed: given back. A charge with an open dispute stays disputed and doesn’t lock, even after its horizon passes, until the dispute is decided.
Decimal string. Credits for prepaid plans; minor units for postpaid plans.
What shows an outcome happened, stamped on the outcome charge. Keep it short and factual; it is shown to people deciding disputes. Free text is sanitized before it reaches dashboards or agent tools.
Why the charge locked. reversal_horizon: the horizon passed. dispute_upheld: a dispute held the lock past the horizon and was decided uphold, which is shown as “locked after dispute”. Only when locked.