Browse developer documentation
Get started
Tracker and integration routes
Understand the remaining /api/v1 routes and the supported workflow for each.
Use the endpoint's supported access path
The endpoint reference covers the public REST operations for custom integrations, plus the public tracker collection contracts. The table below accounts for the remaining /api/v1 routes. A /api/v1 prefix alone does not make a route a workspace-key API.
Dashboard routes use the signed-in Attriboo session and current website permissions. Provider callback and webhook routes are managed by the built-in integration and use provider-specific verification. Do not substitute a workspace Bearer key or send arbitrary normalized payloads to those routes.
| Methods and paths | Supported workflow |
|---|---|
| GET, POST /state | Dashboard workspace state and actions; signed-in session |
| GET /dashboard-report | Dashboard reports; signed-in session and website access |
| GET /activity | Dashboard live activity; signed-in session and website access |
| GET, POST, DELETE /imports | Dashboard CSV preview/import/removal; owners/admins for changes |
| POST /privacy | Dashboard privacy controls; session and website authorization |
| GET, POST /cookieless-settings | Dashboard daily-estimate controls; session, and same-origin acknowledgement for changes |
| GET, POST /demo/state | Public demo interactions using sample activity |
| GET /ads/{platform}/start, GET /ads/{platform}/callback | Start and finish an approved ad-platform connection from Setup |
| GET /integrations/stripe/config, GET /integrations/stripe/install, GET /integrations/stripe/callback | Stripe connection discovery and interactive sign-in flow |
| POST /integrations/stripe/webhooks | Stripe-managed application events; provider verification |
| GET /integrations/shopify/config, GET /integrations/shopify/install, GET /integrations/shopify/callback | Shopify connection discovery and installation flow |
| POST /integrations/shopify/webhooks | Shopify-managed application events; provider verification |
| POST /webhooks/stripe/{siteId}, /webhooks/shopify/{siteId}, /webhooks/lemonsqueezy/{siteId}, /webhooks/polar/{siteId}, /webhooks/paddle/{siteId}, /webhooks/paypal/{siteId} | Native payment notifications configured through Setup; provider payload and signature/verification, not normalized payment bodies |
Browser tracker access
The browser tracker posts to /collect, /cookieless and /poll; each has an endpoint page in this reference. Use the official script for ordinary installation so consent choices, visitor IDs, navigation and checkout behavior stay coordinated.
OPTIONS preflight handlers are transport support, not separate data operations. Public collection uses website IDs and never requires exposing a workspace key. The report API is a separate authenticated server interface.