Inspect your API calls with Request Logs in the Developer Portal
The Developer Portal now features Request Logs, a powerful new tool that lets you search and inspect the API calls your integration makes to the marketplace, complete with status, timing, headers, and payloads.
Inspect your API calls
Request Logs provides a searchable history of your API calls, making it easier to troubleshoot issues without needing to contact support. When an API call fails or behaves unexpectedly, you can look up the call by its x-request-id and see exactly what was sent and received.
Every call your project's API users make to marketplace APIs is logged across all marketplaces for 14 days. The only exceptions are public endpoints that don't require a session, such as authentication calls.
What gets logged
Each log entry includes:
- Request ID, time, and duration
- Status code and, for failed calls, the error code
- Method, endpoint, and query parameters
- API user, project code, and marketplace
- IP address the call came from
user-agentandcontent-typerequest headers
Request payloads are stored for POST calls. Response payloads and limited response headers are stored for POST calls and failed GET calls. Successful GET calls do not store response payloads or headers.
Finding and inspecting a request
You can find requests by their x-request-id or by applying filters for time, API user, status (success or failure), method (GET or POST), and endpoint. Once found, you can inspect the full details, including request and response payloads, and headers.
For a detailed guide, see Find and inspect a request.
Developer Portal updates
Request Logs replaces the previous Debugging Session feature, offering a more comprehensive and persistent view of your API traffic.
You can find Request Logs in the Developer Portal under Monitoring → Logs Dashboard. The Developer Portal overview has also been updated to reflect this new feature, and the path to Rate Limit Analytics is now Monitoring → Rate Limit Analytics.