Skip to main content
Every endpoint requires an API key. The same key identifies you and determines which endpoints you can call.

Getting a key

Once Syrto has provisioned an API for your organization, admins create and revoke API keys in the Syrto dashboard. Each key is scoped to your organization.

Sending your key

Pass the key as a bearer token in the Authorization header:
Keys begin with sk_. Keep them secret - a key grants access to your data and consumes your usage. Send every request over HTTPS, and never place a key in a URL. The examples in these docs read the key from a SYRTO_API_KEY environment variable, so you can export it once and run any example:

Authentication errors

A 503 auth_unavailable means the service could not verify your key right now, not that your key is wrong. Retry with backoff; rotating the key won’t help.
Each error response follows the standard error envelope:

Your endpoints and spec

Your key is scoped to the endpoints included in your plan. To see exactly which endpoints and schemas your key can access, fetch your own OpenAPI spec - it is generated per key and contains only the endpoints you’re offered.