Skip to main content
The API request log records every call to the public API, together with its request and response bodies. Each entry links to what the call created: the email, the event, the contact or the journey run. Use it to answer questions like “why did this customer get that email, with which data, and from which key?” without digging through your own application logs.
Opening the API log needs the API keys: manage permission: workspace Owners, Admins, or a custom role that grants it.

​
Open the log

Go to Settings → Developers → API log. Calls are listed newest first, with these columns: Click Load more at the bottom to page back through older calls.

​
Find a specific call

  • Status: choose All statuses, 2xx, 4xx or 5xx. Choose 4xx to find calls your app sent incorrectly.
  • Path: choose All paths or one API area, such as /api/v1/transactional, /api/v1/events, /api/v1/contacts, /api/v1/lists, /api/v1/webhooks, /api/public/events, /api/public/journeys/trigger, /api/forms or /api/mcp.
  • Search: enter a recipient address, an external id (for example the order id you sent as externalId) or a record id, then click Search.

​
Inspect a call

Click a row to open its details:
  • The Request body and Response body, formatted as JSON (or No body).
  • Produced: what the call created. The Message (opens it in the message log) and the Contact are links. The Event and the Journey run are shown by their id.
It also works the other way round: in Analytics → Message Log, a transactional message’s details include a link to Open the API request that created this message.

​
What is recorded

Not recorded: activity in the app itself, website page-view beacons, incoming webhooks from email providers or Shopify, and calls with an unknown key (they cannot be attributed to a workspace).

​
Privacy and size limits

  • Secrets are redacted. Any field whose name looks like a password, secret, token, authorization header, API key or credential is stored as [redacted].
  • Attachments are not stored. Only the length of an attachment’s content is kept.
  • Large bodies are truncated. Request bodies over 64 KB and response bodies over 16 KB are stored as a shortened preview marked _truncated.
Request bodies can contain personal data, such as the recipient address, the contact fields you send and your data payload. Anyone who can open the API log can read it. Keep that in mind when you decide who gets the Owner or Admin role, or a custom role with API keys: manage.

​
Retention

Requests are kept for 90 days and then deleted automatically.

​
Troubleshooting with the log