API keys

Snow’s server-side APIs need a key so the collector knows the request really came from you. A single API key authenticates both the Server-side events API and the Identify API.

Creating a key

Create an API key in your site’s settings. Each key:

• belongs to one site and is shown in the format snw_live_….
• works for both server-side endpoints: it carries the events:write and identify:write scopes, so the same key can send events and identify users.
• is shown in full only once, right after you create it. Copy it and store it somewhere safe (a secrets manager or environment variable). Snow never shows it again; afterwards you only see a short prefix so you can tell keys apart.

You can create as many keys as you want (handy for separate services, or for rotating without downtime) and revoke any of them at any time. Revoking takes effect immediately and can’t be undone; a revoked key stops working at once.

Using a key

Send the key as a Bearer token in the Authorization header:

Authorization: Bearer snw_live_your_key

See each API’s reference for the full request format:

Legacy identify keys

Earlier versions used a separate, single-purpose identify key (format ski_…) only for the Identify API. Those keys still work, so existing integrations keep running, but new setups don’t need one: use a single snw_live_ API key for both events and identify.