Use the Sessions API to retrieve durable result summaries after the browser handoff completes.Documentation Index
Fetch the complete documentation index at: https://tripwirejs.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint summary
| Method | Path | Purpose |
|---|---|---|
GET | /v1/sessions | List sessions with the latest result summary |
GET | /v1/sessions/:sessionId | Retrieve deep investigation detail for one session |
GET /v1/sessions
Returns one row per session with the latest decision summary.
Supported query parameters:
limitcursorverdictsearch
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:
decisionis the current session outcome in public, action-oriented terms.automation_statusmaps toautomated,human, oruncertain, whiledecision_statustells you whether the current result ispreliminaryorfinal.highlightsis a curated explanation layer capped at five items, including both concerning and reassuring findings.automation,web_bot_auth,network, andruntime_integritysummarize the strongest fraud and classification context.visitor_fingerprintandconnection_fingerprintprovide continuity and transport identity context.signals_firedis the structured machine-usable signal summary;highlightsis the editorial explanation layer.client_telemetryis 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.