Request logs

Resia keeps a log of the requests your organization sends to the API, and of the webhook requests Resia sends to your servers. Use it to see exactly what was sent and what came back.

List requests

curl --fail-with-body --silent --show-error --get \
  "$RESIA_API_BASE/v1/request-logs" \
  --header "Authorization: Bearer $RESIA_API_KEY" \
  --data-urlencode 'kind=webhook' \
  --data-urlencode 'limit=20'

The list is newest first. Each item has the request_id, kind, method, route, status_code, and created_at. Follow next_cursor for the next page.

Filters:

Parameter	What it does
`kind`	`api` for requests you sent, or `webhook` for requests Resia sent to you.
`status_code`	Only requests with this status, such as `422`. A webhook that never answered has no status and does not match.
`route`, `method`	Only requests to this endpoint.
`created_after`, `created_before`	A time range.

Read one request

curl --fail-with-body --silent --show-error \
  "$RESIA_API_BASE/v1/request-logs/REQUEST_ID" \
  --header "Authorization: Bearer $RESIA_API_KEY"

This adds the complete request_body and response_body. Resia replaces its own credentials in a body with [redacted]. Your own field values are stored as you sent them.

Every API response has an X-Request-ID header, and every error body repeats it as request_id. It is the same ID as the log entry, so you can go from any response straight to the full request.

Common uses

A webhook did not arrive: list kind=webhook and read the attempts. Check the status your server returned, or whether it timed out.
A 422 you do not understand: filter by status_code=422 and read the response body.
Support: send the request_id to support@resia.ai. Do not send keys or private call content.

Requests to person-only endpoints, such as member and API key management, are not logged.

API reference: Request logs

Billing

Build with AI assistants