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. Webhook events and custom tool calls both have the kind webhook. |
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]. Resia also replaces each password value, such as the password of a SIP connection, with [redacted]. This rule does not apply inside the objects that you define: inputs, analysis, and the parameters of a custom tool. Resia stores those objects as you sent them, also a field named password or secret. Your other 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.
A log entry for a custom tool call shows only the origin of your endpoint as its route: the scheme, the host, and a port other than 443. Resia never stores the full endpoint URL. The request body names the tool.
Each entry has an insito_admin field. It is true when a member of the Resia team sent the request for your organization, for example during support. The entry does not name the person. API keys and invites have equivalent fields: created_by_insito_admin, revoked_by_insito_admin, and invited_by_insito_admin. The invited_by field of such an invite is null.
Common uses
- A webhook did not arrive: list
kind=webhookand read the attempts. Check the status your server returned, or whether it timed out. - A
422you do not understand: filter bystatus_code=422and read the response body. - A custom tool failed: list
kind=webhookand read the entry. It holds the status and the body that your endpoint returned. - Support: send the
request_idto 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

