Request Inspector (merged into API Logs)
The per-request detail view is not a separate Konsole tool — it is part of API Logs.
2 min read
This is not a separate tool
Earlier revisions of this documentation described a "Request Inspector" as a standalone, real-time Konsole tool with its own "Matched Rule" sidebar and a "Replay in Playground" action. Neither exists. Opening any row in API Logs shows you the full detail of that request — headers, body, response, status, duration, and error trace — on the same page. There is no separate URL, no live/streaming view, and no in-app "Playground" to replay into.
Where this content lives now
The full, accurate description of what a request record contains is documented on the API Logs page.
A few things worth calling out explicitly, since they were previously misdescribed here:
- No "Orchestration" section. A request log row carries no routing/provider information. To see which providers were considered for a given payment, look up the same transaction in Routing Log — a separate record, keyed by transaction, not something attached to a request row.
- No
replayedidempotency badge. Request records don't carry an idempotency-replay indicator. - No "Replay in Playground" action. There is no in-app API client to replay into — see API Playground.
- Retention is 90 days by default, in both sandbox and live (configurable via
LOG_RETENTION_DAYS, enforced by a scheduledlogs:prunejob) — not "30 days in production, 7 days in test."