Skip to main content
GET
Get one API request, including its error body
Returns one entry of the API request log, with the details that the list leaves out: the caller’s ip, the userAgent and, for failed requests, the errorBody. The id is the same value the API returned in the X-Request-Id header of that response. If something failed, copy the ID from the header and look it up here.

Authentication

Accepts either:
  • An API key (X-API-Key: sk_...) with the read:request-logs scope — the organization is resolved from the key itself.
  • A Supabase Bearer session (Authorization: Bearer <token>) with the X-Organization-Id: <org-id> header — the authenticated user must be an owner or admin of that organization.

About errorBody

  • It is present only when statusCode is 400 or higher. Successful responses never store a body.
  • RFCs found in it are masked as ***RFC***.
  • It holds at most 2 KB. When the body is longer, you get { "truncated": true, "preview": "…" } instead.

Example Request

Example Response

Common Errors

401 Unauthorized

Missing or invalid Bearer token / API key.

403 Forbidden

The authenticated user is not an owner or admin of the organization, or the API key does not have the read:request-logs scope.

404 Not Found

The record does not exist, has passed the 30-day retention, or belongs to another organization.

Authorizations

X-API-Key
string
header
required

API Key for authentication (format: sk_...)

Headers

X-Organization-Id
string

Required for Supabase session auth (owner or admin). Ignored with an API key.

Path Parameters

id
string
required

Response

id
string
required

También es el header X-Request-Id

createdAt
string
required
method
string
required
route
string
required
Example:

"/invoices/:uuid"

path
string
required
statusCode
number
required
durationMs
number
required
environment
enum<string> | null
Available options:
sandbox,
production
channel
object | null
authFailure
object | null
apiKey
object | null
ip
object | null
userAgent
object | null
errorBody
object | null

Cuerpo del error (solo status ≥ 400), con RFC enmascarados y máximo 2 KB