Create an outcome definition
Defines one kind of outcome you charge for: the event that reports it, the criteria you agreed with your customers, the two clocks, the reversal rules and the dispute settings. Plans set its price. The clocks have no silent default: send them, or send a preset from GET /v1/outcome_definition_presets and the server fills in the values you left out and stores them explicitly. Values outside the recommended ranges are accepted and come back as warnings.
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.
Request
The track() event that reports this outcome. Unique across outcome definitions.
A preset key, such as support_chat, that fills in confirmation_window, reversal_horizon and dispute_settings where you don’t send them. The stored definition holds explicit values and echoes the preset’s key, so changing a preset later never changes it.
How long a new charge stays pending before it confirms by default, as an ISO 8601 duration from PT0S to P30D. Required unless preset is sent. Recommended PT1H to P7D; outside that range the response carries a warning.
How long after confirmation a charge can still be reversed, as an ISO 8601 duration from PT0S to P180D. After it passes, the charge locks, unless a dispute is still open. Required unless preset is sent. Recommended P7D to P90D; outside that range the response carries a warning.