The SportQuanta API uses workspace API tokens for authentication. Send your token as a bearer token in the Authorization header on every request.

Getting a token

API tokens are issued per workspace from your SportQuanta dashboard. Each token is tied to one organization and counts against that organization’s monthly quota. Visit sportquanta.com to create one.
Treat your API token like a password. It carries your organization’s quota and billing. Never commit it to source control or embed it in client-side or mobile app code — proxy requests through your own backend instead.

The Authorization header

A complete header looks like:
Quota and rate limits accrue at the organization level, not per token. Rotating or adding tokens does not reset or multiply your limits.

Scopes

Some operations require the token to carry a specific scope. If your token is valid but lacks the scope an endpoint requires, the API responds with 403 and the error code insufficient_scope. Contact your workspace admin or support@sportquanta.com to adjust a token’s scopes.

Failure modes

All auth failures use the standard error envelope:

What doesn’t need a token to count against quota

Authentication is always required, but not every authenticated call is billed. Catalog endpoints — /v1/sports, /v1/leagues, /v1/bookmakers, and prop/odds market catalogs — are free and don’t consume your monthly quota. Per-league data reads are billed. See Rate Limits & Quota for details.