Logs

The Logs page at /logs lists every request made with one of your API keys: method, path, status code, duration, which key made it, and when. Use it to find out why an integration is failing without adding logging to your own code.

• Filter by status (success, 4xx, 5xx), API key, path, and period (24 hours, 7 days or 30 days).
• Click a row to see the request ID, the client's user agent (the SDKs send their name and version), and — for failed requests — the request body you sent and the error response you got back.
• Share the request ID with support. It is the same value returned in the X-Request-Id response header, so it links a failing call to our own logs.

What is and isn't logged

• Only requests authenticated with an API key are logged, including test-mode keys. Requests with a missing or invalid key have no workspace to be logged under, and actions you take in the dashboard are not listed.
• Request and response bodies are kept only for failed requests (status 400 or above). Attachment content is replaced with [omitted], and bodies over 16 KB are truncated.
• Headers are never stored, so your API key does not appear in the logs.
• Logs are kept for 30 days on every plan, then deleted.
• New requests appear within a few seconds.