Skip to main content
Use the Sessions API to retrieve stored result summaries after the browser handoff completes.
Sessions endpoints require a secret key and never return collect-time sealed handoff tokens.

Endpoint summary

GET /v1/sessions

Returns one row per session with the latest decision summary. Supported query parameters:
  • limit
  • cursor
  • verdict
  • search
Example response:

GET /v1/sessions/:sessionId

Returns the full public investigation view for one session. The response is intentionally ordered so the most actionable fraud analysis appears first, followed by continuity context, then structured evidence and lower-level telemetry. Unlike GET /v1/sessions, which stays a compact summary surface with latest_decision, session detail uses the richer decision, highlights, signals_fired, and client_telemetry model shown below. Example response:

PATCH /v1/sessions/:sessionId

Sets or clears client_user_id, the ID of the end user in your own database. This is customer-supplied linkage only: it does not affect scoring, visitor fingerprints, sealed tokens, or browser/native SDK behavior. Requires a secret key with the sessions:update scope.
Send null to clear it:
The response is the same session detail resource returned by GET /v1/sessions/:sessionId, with the updated client_user_id. Response fields are grouped by purpose:
  • decision is the current session outcome in public, action-oriented terms. automation_status maps to automated, human, or uncertain, while decision_status tells you whether the current result is preliminary or final.
  • highlights is a curated explanation layer capped at five items, including both concerning and reassuring findings.
  • automation, web_bot_auth, network, and runtime_integrity summarize the strongest fraud and classification context.
  • visitor_fingerprint and connection_fingerprint provide continuity and transport identity context.
  • signals_fired is the structured machine-usable signal summary; highlights is the editorial explanation layer.
  • client_telemetry is curated lower-level client telemetry for investigations. It is not a verbatim raw probe dump.
signals_fired.signal and highlights.evidence.signal are friendly string slugs. They are response values, not an exhaustive documented enum registry.