Base URL
Authentication
All requests require a bearer token. See the Authentication guide for key types, scopes, and rotation.Conventions
The Main API is rolling out a set of wire-level conventions in stages. Per-IP edge rate limits, cursor pagination, and theX-Request-Id correlation header are live today. Per-key rate limits with read/write split, the MCP boost, Idempotency-Key enforcement, full Spotzee-Version validation, and the RFC 7807 error envelope ship in a future release. Each guide flags the live-vs-rolling-out state for its concern.
Endpoints
Endpoint pages are auto-generated from the OpenAPI specification. See the sidebar for the full list, grouped by resource (Users, CRM, Lists, Subscriptions, Campaigns, Journeys, Templates, Events, Tags, Projects, API keys, Organisation).
CRM access
CRM endpoints use the project-scoped/client surface. Generated CRM paths such as /crm/contacts are relative to:
sk_) in the Authorization header. CRM reads require a secret project key. CRM writes require a secret project key with the project editor role or higher.
Public CRM properties appear in each record’s properties object. Hidden and classified CRM properties are not exposed in CRM API responses.
OpenAPI spec URL: https://apix.spotzee.com/api/openapi.json
Next steps
CRM guide
Organise contacts, companies, activities, and pipeline stages.
Authentication
Key types, scopes, and rotation.
Errors
Status codes and the
code catalogue.