Client / BrowserClient / Spotzee classes cover the most common browser-side flows: identify, alias, track, register devices, fetch notifications. For server-side integrations, agentic workloads, or anywhere you want full type coverage of the API, the SDK ships a generated typed client at the @spotzee/js-sdk/generated subpath.
When to reach for it
You can mix both surfaces in the same project. They share no state.
Set it up
baseUrlpoints at the Main API client surface. Use a publishable key (pk_…) for SDK-style flows or a secret key (sk_…) for full backend access. Read Manage API keys for the distinction.Spotzee-Versionpins your call to a known API release date. Read API versioning for the version model.x-spotzee-client-typeidentifies your traffic. The SDK suggestssdk-js; for an agent or automation, useagentor your own descriptive value. Read Identify your API client type.
Call any operation
Every operation in the OpenAPI spec is exposed as a function on theSpotzee namespace. Each returns { data, error } so you can branch on success without try/catch.
2026-04-28 release: code, message, type, request_id. Use code for programmatic branching; message is for humans; request_id goes to support.
Use the exported types
Every component schema in the OpenAPI spec is exposed as a static type under theSpotzee namespace:
Pagination
List operations return cursor-paginated results. Walk the cursor explicitly:Regenerating the client
The generated source is checked in. To regenerate against the live spec athttps://apix.spotzee.com/api/openapi.json:
Spotzee-Version declared in the SDK’s source.
Mixing surfaces
You can call the typed client from a backend that also uses the ergonomic surface in a frontend bundle. They don’t conflict.Next steps
Main API reference
Browse the full operation catalogue and request shapes.
Send events from your backend
Recipe for high-volume server-side event ingestion.