HTTP surface reference
Separate tool calls, browser ingestion, user flows and operator endpoints.
On this page
Supported external integration surface
| Endpoint | Purpose | Authentication / caller |
|---|---|---|
| /api/v1/tools | Runtime tool catalog | Bearer credential |
| /api/v1/tools/<name> | Shared report/management tool | Bearer; POST for writes |
| /api/v1/mcp | Streamable HTTP MCP | OAuth or bearer key |
| /weeveo.js | Browser SDK | Public asset; project configured in attributes |
| /recorder.js | Optional recorder | Public asset; server settings and purpose consent |
| /api/v1/webhooks/<gateway> | Payment event ingestion | Provider-specific verification and site URL |
| /.well-known/oauth-* and /oauth/* | Discovery and authorization | OAuth protocol / user consent |
Browser and dashboard endpoints
The tracker uses /api/v1/collect. Optional capture uses /api/v1/record and recorder configuration under /api/v1/recorder/<projectId>. Dashboard live updates use /api/v1/live/<projectId> and authenticated project realtime/status/activity routes. These are implementation transports, not a general server-side ingestion SDK: do not forge browser consent or identity payloads. Use the browser SDK for permitted tracking and shared tools for querying.
Dashboard-only routes also handle project export, replay retrieval, heatmap snapshots, private agent chats, integration setup and authenticated privacy export. They enforce their own session/role/consent policies; they are not interchangeable with API-key tool endpoints.
Public report endpoints
Share links, embed pages and badge assets use opaque tokens created by the sharing feature. Revoking a token removes that link's public access. These are public aggregate outputs, not authenticated personal-record APIs.
Operator-only endpoints
/api/v1/cron/<job> runs reconcile, anomalies, digest or cleanup with CRON_SECRET authorization. Storage upload/signing, email delivery and health endpoints serve application operations with their own checks. Do not distribute internal credentials to an agent or call internal routes instead of the supported tools.
Exact inputs
The tool reference is the complete argument contract for the supported MCP/REST tools. The JSON reference exports the same documentation schemas without customer data.
Still looking for an answer? Try troubleshooting or get in touch.