Skip to main content

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.

Tripwire’s public API covers four product surfaces:
  • Sessions — durable session result readback for backend verification and audit.
  • Fingerprints — durable visitor fingerprint readback for cross-session correlation.
  • Gate — the Gate registry, agentic signup, agent tokens, and dashboard login sessions.
  • Organizations — organization, membership, and API key lifecycle.

​
Base URLs

Managed Tripwire uses separate hosts for the CDN-hosted browser agent and the REST API. 
Browser agent: https://cdn.tripwirejs.com/t.js
API base:      https://api.tripwirejs.com
Every public endpoint lives under /v1/. See Versioning for how the API evolves.

​
Cross-cutting conventions

A handful of concerns apply to every endpoint. They have dedicated pages so they’re easy to link to and easy to keep accurate:

Authentication

Key types, scopes, and lifecycle. Start here.

Errors

Error envelope shape, status codes, retry semantics.

Pagination

Cursor-based pagination on every list endpoint.

Rate limits

Organization defaults, response headers, retry strategy.

Versioning

What’s additive, what’s breaking, and how to pin.

Security and privacy

Crypto, infrastructure, and what you should disclose.

​
Endpoint groups

Sessions

Read the latest durable session result from your backend with a secret key.

Visitor fingerprints

Inspect durable visitor fingerprints with a secret key.

Gate

Browse the Gate registry, manage services, create signup sessions, verify agent tokens, consume login codes.

Organizations

Create organizations, provision key pairs, and rotate or revoke keys.