API
API Overview
Use website API keys for public API routes. Dashboard routes require a signed-in user session.
Authentication
X-API-Key: YOUR_WEBSITE_API_KEY is also accepted for public API v1 routes.
http
Authorization: Bearer YOUR_WEBSITE_API_KEYPublic routes
| Method | Route | Purpose |
|---|---|---|
| POST | /api/track | Tracker ingestion |
| POST | /api/track-payment | Hosted checkout fallback ingestion |
| POST | /api/v1/goals | Create server-side goals |
| DELETE | /api/v1/goals | Delete matching goals |
| POST | /api/v1/payments | Create server-side payments |
| DELETE | /api/v1/payments | Delete matching payments |
| GET | /api/v1/analytics/* | Query analytics metrics |
| GET | /api/v1/visitors/{id} | Query one visitor timeline |
Common query filters
from/tofilter by reporting date (YYYY-MM-DD).startAt/endAtare accepted aliases for date or ISO 8601 date-time inputs.timezonecontrols day boundaries.country,region,city,referrer,ref,via,source,device_type,device,browser,os,utm_source,utm_medium,utm_campaign,utm_term,utm_content,page,entry_page,hostname, andgoal_idfilter analytics responses where supported.