Retrieve a request log
Look up a request by the Request-Id header or the request_id in an error.
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 request ID (req_...).
Response
A stable, machine-readable error code. New codes may be added.
The first characters of the key, enough to tell keys apart. Absent when a signed-in person made the request from the dashboard, since no key was involved.
True when the request was sent with Runledger-Dry-Run: true and nothing was written. Absent otherwise.
The request body as sent, with each secret (a signing secret, or a link that grants access) replaced by [redacted] before it was stored.
The response body as returned, with each secret (a signing secret, or a link that grants access) replaced by [redacted] before it was stored.