Usage event
Looks up one request by the X-Request-Id header its response
carried. Returns every field of an event in GET /account/usage/events
plus what was sent:
request: the body, query parameters and path parameters.headers: the request headers, withauthorizationandapikeyshown as<redacted>.response: the error body a failed request got back, redacted. It is JSON when the body was JSON, and a string when it was not or was cut at 32 KB. It isnullon a success and on a429.
A request id that belongs to another team returns 404, the same as
one that never existed.
This endpoint is free: the response carries no X-Credits-Used
header. It shares a limit of 60 requests per minute with the other
/account/usage/* endpoints.
Authorizations
API key passed as a Bearer token in the Authorization header.
Headers
API version to use. This endpoint currently requires 2025-11-01. Requests without the header, or with any other value, return 400.
2025-11-01 "2025-11-01"
Path Parameters
The X-Request-Id response header of the request, also returned as event_id by GET /account/usage/events.
256Response
The event, with the stored request.
An event plus the request that was stored for it.
The request id, the same value as the X-Request-Id header on the original response.
"678a3646-371d-4f81-b5c3-488fdda81e21"
When the request was made, ISO 8601 in UTC with a +00:00 offset.
"2026-09-24T03:24:40.229000+00:00"
Your team's id.
1318
The user on your team who made the request.
1318
The API key that made the request. null when the request is not tied to a key, such as a watch run or a request refused with a 429.
170
Where the request came from. Values seen today are api, mcp, cli, dashboard, batch, watcher, export, and gateway for a request refused before it reached the API, such as a 429.
"api"
The client detected from the request, for example python, node, curl or claude-code. It comes from the MCP client tag, the CLI's user agent, or a category based on your User-Agent header. New values can appear at any time. Empty for batch jobs, watches and exports, and usually for requests refused with a 429.
"curl"
The User-Agent header you sent.
"curl/8.7.1"
The IP address the request came from.
"203.0.113.10"
The product the request belongs to, for example person_enrich.
"person_enrich"
The endpoint, as a route template when it has path parameters, for example /watch/person/:watch_id/runs. The actual values are in request.path_params on the single-event endpoint.
"/person/enrich"
The HTTP method.
"POST"
The x-api-version header you sent.
"2025-11-01"
The status code returned.
200
2xx, 3xx, 4xx or 5xx.
"2xx"
The error.type returned on a failure, for example invalid_request. Empty on a success.
""
The error group the request belongs to in GET /account/usage/errors. Empty on a success and on a 429.
""
Results the request returned.
1
Time the request took on the server, in milliseconds.
413.39
Credits charged, the same number the original response returned in X-Credits-Used.
2
The charge lines. Their credits add up to credits_used, and lines charged at 0 credits are kept. Empty when nothing was charged.
Ids of the job that made the request, when there is one, such as batch_job_id, watch_id, export_id and export_run_id. Empty for a direct API call.
What was sent. null when the stored copy is no longer available.
The request headers, with authorization and apikey shown as <redacted>.
The error body a failed request got back, redacted. JSON when it was JSON, a string when it was not or was cut at 32 KB. null on a success and on a 429.

