Request logs
Read the record of evaluation requests your workspace made, including failed ones.
Request logs record your workspace's evaluation requests, successful and failed: when each was recorded, the HTTP status it returned and, for a failure, its public error code. Every AbuseZero REST API response carries an X-Request-ID header, and every error repeats it as request_id. The request log ID is that value with a req_ prefix, for requests made over the REST API and through the AbuseZero MCP server, so a request your servers recorded can be looked up here directly.
Two kinds of request aren't logged: requests whose credential never authenticated, because they belong to no workspace, and rate-limited requests (429). Keep the request_id of any request, and include it whenever you contact AbuseZero about it.
Examples on this page use a server client:
import { AbuseZero } from "abusezero/server";
const abusezero = new AbuseZero({ key: process.env.ABUSEZERO_SECRET_KEY!, outage: "throw" });The request log object
{
"object": "request_log",
"id": "req_7d0e5c2a-1f4b-4e8a-b6c3-9a2d5e0f1b74",
"status": 200,
"code": null,
"created_at": "2026-10-29T14:02:19.000Z"
}| Field | Type | Description |
|---|---|---|
object | "request_log" | The object type. |
id | string | The request log ID, starting with req_. |
status | integer | The HTTP status AbuseZero returned. |
code | string or null | The error code returned, or null when the request succeeded. |
created_at | string | When the request was recorded. |
List request logs
Returns request logs newest first.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
GET | /v1/request-logs | request_logs:read | Not used |
Also available as abusezero request-logs list in the AbuseZero CLI, abusezero_list_request_logs on the AbuseZero MCP server and requestLogs() in the AbuseZero Node.js SDK.
Query parameters
| Parameter | Type | Required | Limits | Description |
|---|---|---|---|---|
limit | integer | No | 1 to 100, default 50 | How many request logs to return. |
cursor | string | No | The next_cursor from the previous page, unchanged. |
Example
const page = await abusezero.requestLogs({ limit: 100 });Response
Returns 200.
{
"object": "list",
"data": [
{
"object": "request_log",
"id": "req_7d0e5c2a-1f4b-4e8a-b6c3-9a2d5e0f1b74",
"status": 200,
"code": null,
"created_at": "2026-10-29T14:02:19.000Z"
},
{
"object": "request_log",
"id": "req_4b2d6f8a-0c1e-4a3b-9d5f-7e8a1c3b5d02",
"status": 404,
"code": "BENEFIT_NOT_FOUND",
"created_at": "2026-10-29T14:01:47.000Z"
}
],
"next_cursor": "…"
}When next_cursor is a string, pass it as cursor to read the next page. See Pagination.
Retrieve a request log
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
GET | /v1/request-logs/{id} | request_logs:read | Not used |
Also available as abusezero request-logs get in the AbuseZero CLI, abusezero_get_request_log on the AbuseZero MCP server and call() in the AbuseZero Node.js SDK.
Path parameters
| Parameter | Type | Description |
|---|---|---|
id | string | The request log ID: req_ followed by the request's X-Request-ID. |
Example
const log = await abusezero.call("/v1/request-logs/req_7d0e5c2a-1f4b-4e8a-b6c3-9a2d5e0f1b74");Response
Returns 200 with a request log object.
Errors
| Code | Status | Meaning |
|---|---|---|
RESOURCE_NOT_FOUND | 404 | No request log with this ID exists in the workspace. |
For every other code, see REST API errors.
Related
How is this guide?
Last updated on