Get API request log entry detail

GET https://app.speybooks.com/api/v1/api-request-log/{id}

Full detail of a single API request log entry including request headers, request body, and response body. Use for debugging specific failed requests or auditing API usage.

Returns 404 if the entry does not exist or belongs to another organisation.

Path parameters

id integer required

Request log entry ID.

Response

200 Full request log entry including request headers, request body, and response body.

Show response fields

apiKeyId integer

createdAt string date-time

id integer

ipAddress string

keyName string

keyPreview string

method string

path string

requestBody object

Show child attributes

contactId string

issueDate string

requestHeaders object

Show child attributes

authorization string

content-type string

responseBody object

Show child attributes

error object

Show child attributes

code string

message string

success boolean

responseTimeMs integer

statusCode integer

userAgent string

Error codes

404 Request log entry not found or does not belong to this organisation.

Request GET /v1/api-request-log/{id} curl

curl https://api.speybooks.com/v1/api-request-log/42 \
  -H "Authorization: Bearer sk_test_..."

Response 200

{
  "success": true,
  "data": {
    "id": 42,
    "apiKeyId": 7,
    "keyPreview": "sk_live_...Ab3x",
    "keyName": "Production CI/CD",
    "method": "POST",
    "path": "/v1/invoices",
    "statusCode": 400,
    "responseTimeMs": 23,
    "ipAddress": "203.0.113.42",
    "userAgent": "node-fetch/3.3.2",
    "requestHeaders": {
      "content-type": "application/json",
      "authorization": "[REDACTED]"
    },
    "requestBody": {
      "contactId": "invalid_format",
      "issueDate": "2026-02-19"
    },
    "responseBody": {
      "success": false,
      "error": {
        "code": "invalid_id",
        "message": "Invalid ID format: invalid_format"
      }
    },
    "createdAt": "2026-02-19T12:00:00.000Z"
  }
}