Logs - Ozi

The Logs page records every call made to the Ozi API with an API key. It is the first place to look when an integration is misbehaving: you can see what was sent, what came back, how long it took and where it came from.

What is recorded

Field	Meaning
Endpoint	The path as requested, e.g. `/emails/abc123`
Route	The endpoint pattern that handled it, e.g. `/emails/:emailId`, so calls group by endpoint
Status	The HTTP status returned
Error code	The API’s own error code when a call failed, such as `RATE_LIMITED` or `NOT_FOUND`
Duration	Time to respond, in milliseconds
Source	`API` for direct calls, `SDK` for the official SDKs, `SMTP proxy` for mail relayed through SMTP
API key	Which key made the call
User agent	What the client identified itself as

Request and response bodies are not stored. The log is about what happened, not what was said.

Filtering

Filter by time window, status class (2xx, 4xx, 5xx), method, user agent or source, and search by endpoint, error code or IP address. Export writes the current view to CSV, up to 5,000 rows.

Retention

Logs are kept for thirty days and pruned nightly. Calls that fail authentication are not recorded: without a valid key there is no team to file them under.

The source column depends on the client identifying itself. The JavaScript SDK sends ozi-js/<version> and the SMTP proxy sends ozi-smtp-proxy; a client that sends its own User-Agent shows as API.