Usage, request log and error log
Updated
What the Usage page shows#
Usage in the top navigation shows what your keys have actually been doing.
| Section | Contents |
|---|---|
| Requests / Failed / Avg latency | Totals for the selected range |
| Requests per day | Stacked bars — succeeded in green, failed in red |
| Recent requests | The last 50 calls: time, key, endpoint, document type, HTTP status, latency |
| Error log | The last 50 failures with the error code, a short message and the request id |
Use the key selector to focus on one key (revoked and rotated keys are included, so history is never lost) and the 7d / 30d / 90d buttons to change the range.
What counts as a request#
Every authenticated call to documents, process and result is one row, whatever its outcome. A multi-page document therefore appears as one documents call (status 202), one process call per chunk, and one result call. Credits are a different measure — they are per page — see rate limits and quotas.
Reading the error log#
The Code column is the same error.code the API returned; the meaning of each is in error codes. The request id matches the one in the API response and is what to quote when you write to support.
store_db: true, so there is nothing to
download here. Times are shown in your browser's timezone.Something wrong or missing on this page? Tell us.