Requests Log
Use Settings → Customer settings → API Management → Requests Log to inspect calls made with Admin API keys for your customer account. This is useful when an integration fails authentication, lacks a scope, or sends invalid data.
Find a Request
The page initially shows the last 30 days. You can select the last 24 hours, 7 days, or 30 days, filter by key and HTTP method, choose successful or failed responses, and search endpoint paths or key names.
Each row includes a timestamp, key, method, endpoint, HTTP status, and latency. Select a row to open Request Details.
Read the Details
The detail view includes the request ID, authorization result, required scope, scope-check result, and any captured error information. Failed requests can include request and response bodies. Successful requests do not store those bodies.
For a scope_denied error, compare the operation's required scope with the key's scopes. For an expired or revoked key, create a replacement and update your integration. See the Authorization Guide.
When contacting support, include the request ID, timestamp, endpoint, and error code. Keep API-key secrets out of support messages.
Coverage and Retention
- Logs cover Admin API calls associated with a recognized key. Embed API calls are not included here.
- Missing, malformed, or unknown keys cannot be associated with your account and do not appear. Requests using a recognized revoked or expired key can appear.
- Logging is best effort, so a missing entry does not prove that no request was made.
- Stored logs have a default retention period of 90 days. The UI's 30-day view is a filter, not the retention period.
If no entry appears, first check your integration's response, URL, and authentication header. Verify you are using an Admin key with Authorization: Bearer … at the Admin API host.