API request logs let you inspect recent public API traffic made with the current API key. Use them to debug auth failures, repeated retries, unexpected 4xx/5xx responses, which resource a request targeted, and whether a sandbox-bound test key is hitting the expected sandbox routes.
This surface is intentionally scoped to the calling key (it is not a merchant-wide audit log across every key). The list returns request summaries only: method, route, status, latency, resource, and error code. The detail endpoint adds redacted headers and, for eligible write requests, redacted request and response bodies, plus a ready-to-run reproduction; credentials, card data, and personal data are always replaced with [REDACTED] before storage. Listing requires the developer.logs.self.read scope and detail requires developer.logs.self.detail.read.
The Debugging guide walks the full workflow, from a request_id to a diagnosis to a resource timeline. Pair it with the Error handling guide to map error codes to fixes, and the Testing guide for the sandbox testing loop.
