What your partners' developers get.

Partners use a portal your team runs.

A sandbox key, shown once.

Copy it when it appears. Spectrum keeps a hash, so nobody can show it to you again.

Keys go in the Authorization header.

Fig 3.1

Sample request

curl https://api.your-domain.example/api/v1/<product>/... \
  -H "Authorization: ApiKey <sandbox-key>"
Illustrative · API credentials, sample data
API credentials table for the sandbox environment, showing a sample client ID, a masked API key and a button to generate a live key.

Production gets its own key.

Developers browse the catalog and read the API docs in the portal, then request access to the API products they need. Your team approves or rejects each request.

Fig 3.2

You set the hourly limit.

Each API product has an hourly limit, and each partner has its own count. Run out and the API answers with a 402 and says when to retry.

Fig 3.3

Sample response at the limit

HTTP/1.1 402
X-Quota-Remaining: 0
Retry-After: <seconds>

{ "title": "QUOTA_EXHAUSTED", ... }

Docs come with the walkthrough.

Evaluating it for your organisation? Bring the developers who'd build against it.

Request a walkthrough