Skip to main content
Every API-key and anonymous public-quote request writes one metadata-only log row. Search it with GET /v1/request-logs, or in the Console under Developers → Requests. Rows with a Quote open the trace view, which follows the request to the pinned Book Version, the outbox events, and every webhook delivery.

​
What is logged — and what is not

Each row records:
Redaction is by construction, not filtering. Logs never contain request or response bodies, factor values, prices, or secrets — the writer only ever receives metadata. Logging is also best-effort: a logging failure never fails your API request.

​
Search the logs

Filters (combine freely): Results come 50 per page, newest first; pass the response’s nextCursor as cursor to page forward. The Console Requests tab exposes the same filters with a “Load more” cursor.

​
The trace view

GET /v1/quote-traces/{quoteIntentId} — or clicking a log row in the Console — returns the full picture for one Quote:
  1. The Quote Intent and its state history.
  2. The Receipt, including the pinned bookVersionId — the exact Book Version the customer was quoted against, even if a newer version has been published since.
  3. The outbox events the Quote emitted.
  4. The webhook deliveries fanned out from those events, per endpoint, with attempt counts, last status, and last error.
The typical support path: a customer reports a failed quote → find the request by requestId or quoteIntentId → open the trace → see the unpriced Receipt’s failure.code, which Book Version was pinned, and whether the webhook notification to your own systems was delivered, retried, or exhausted (and replay it from there if needed).

​
Correlate with your own logs

Two identifiers bridge Kordless and your systems:
  • requestId — returned on every response (x-request-id header and envelope requestId) and stored on the Intent and Receipt as requestCorrelationId. Log it on your side whenever you create a Quote.
  • quoteIntentId — the Quote’s durable id, present on webhook envelopes inside data and filterable in log search.
Include the requestId when contacting support about a request; it resolves to exactly one log row.

​
Next steps

  • Webhooks — delivery envelopes, signing, retries, and replay.
  • Errors — the error codes that appear in errorCode.
  • Browse the full API reference for the request-logs and trace schemas.