API Reference

Snow exposes a small set of public ingestion APIs for getting data into Snow. Most sites only need the tracking snippet, which calls these for you. Reach for the API when you want to send events from a server, a backend job, or a non-browser environment.

Endpoint	Auth	Use it for
`POST /api/collect`	None (public)	The raw page-view / event endpoint the browser snippet uses.
`POST /api/v1/events`	API key	Sending events from your server or backend.
`POST /api/identify`	API key	Attaching an identity (and Stripe customer) to a visitor.

Base URL

All endpoints live on your Snow collector. Throughout these docs that’s:


https://api.snowanalytics.app

Replace it with your own collector URL.

Authentication

/api/collect is public (the browser calls it). The two server-side endpoints use a bearer token in the Authorization header:


Authorization: Bearer YOUR_KEY

A single API key (format snw_live_…), created and managed in the dashboard under API keys, works for both server-side endpoints carrying the events:write and identify:write scopes:

Endpoint	Key
`POST /api/v1/events`	`snw_live_…` (`events:write`)
`POST /api/identify`	`snw_live_…` (`identify:write`; legacy `ski_…` keys also accepted)

Send JSON with Content-Type: application/json. Keep keys secret. Treat them like passwords, and revoke or rotate any that leak.

Reading data: these are write (ingestion) APIs. You view and analyze your data in the dashboard. There isn’t a public token-authenticated read API for reports today.

Rate limits

Each endpoint is rate-limited. See Rate limits & errors for the limits and the error format.