Your past calls
Your own call history, newest first. Free — it reads our table, not the vendor. **`request` and `response` are null unless the deployment enables the call log** (`CALL_LOG_DAYS`, ADR-036), which is off by default. The rest of each row — endpoint, credits, cached, timestamp — has always been recorded and is what billing runs on. Bodies are opt-in per request rather than always included. A page of fifty payloads is megabytes, and a caller listing "what did I call yesterday" wants neither the bytes nor the wait; `include=response` is for the caller who is replaying one. Scoped to `ctx.key.user_id` in the query itself rather than filtered afterwards. That is the difference between a bug that leaks another customer's history and a query that cannot express it.
/v1/usageYour own call history, newest first. Free — it reads our table, not the vendor.
request and response are null unless the deployment enables the call log
(CALL_LOG_DAYS, ADR-036), which is off by default. The rest of each row — endpoint,
credits, cached, timestamp — has always been recorded and is what billing runs on.
Bodies are opt-in per request rather than always included. A page of fifty payloads is
megabytes, and a caller listing "what did I call yesterday" wants neither the bytes nor
the wait; include=response is for the caller who is replaying one.
Scoped to ctx.key.user_id in the query itself rather than filtered afterwards. That is
the difference between a bug that leaks another customer's history and a query that
cannot express it.
Query Parameters
Opaque value from a previous page's next_cursor.
1 <= value <= 20050Set to response to include each call's stored payload. Ignored when the call log is disabled.
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/usage"{ "items": [ { "cached": true, "created_at": "2019-08-24T14:15:22Z", "credits": 0, "endpoint": "string", "platform": "string", "request": {}, "response": {} } ], "next_cursor": "string"}