Skip to navigation

Retrieve a request log

Look up a request by the Request-Id header or the request_id in an error.

Authentication

AuthorizationBearer

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

request_idstringRequired

The request ID (req_...).

Response

The request log.
idstring
object"request_log"
methodstring
pathstring
statusinteger
idempotent_replayedboolean
api_versionstring
duration_msinteger
livemodeboolean
created_atdatetime
error_codeenumOptional

A stable, machine-readable error code. New codes may be added.

idempotency_keystringOptional
api_key_prefixstringOptional

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.

dry_runbooleanOptional

True when the request was sent with Runledger-Dry-Run: true and nothing was written. Absent otherwise.

actorobjectOptional
Who made the request. For an MCP call it names the client and the person it acts for.
sdkobjectOptional
request_bodymap from strings to anyOptional

The request body as sent, with each secret (a signing secret, or a link that grants access) replaced by [redacted] before it was stored.

response_bodymap from strings to anyOptional

The response body as returned, with each secret (a signing secret, or a link that grants access) replaced by [redacted] before it was stored.

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
429
Too Many Requests Error
500
Internal Server Error