Authentication
Send your API key in the Authorization header on every request.
Every request needs an API key. Create one in Settings β API access; see Create and revoke API keys.
Send the key
Put the key in the Authorization header as a bearer token:
GET /api/v1/sites HTTP/1.1
Host: app.seobolt.io
Authorization: Bearer sbk_your_key_here
If your client can't set Authorization, send the key in X-SEObolt-Org-Key instead:
X-SEObolt-Org-Key: sbk_your_key_here
If a request has an Authorization header, that header is used and X-SEObolt-Org-Key is ignored.
Key format
Keys start with sbk_ followed by 43 letters, numbers, - or _. A key in any other format is rejected without being looked up.
When a key is refused
| Status | Code | Why |
|---|---|---|
| 401 | unauthorized | No key, a key in the wrong format, an unknown key or a revoked key |
| 403 | tier_required | The organization's plan is below the one API access needs. The key works again once the plan is restored. |
| 409 | organization_unavailable | The organization has no owner, so its data can't be read |
{ "error": { "code": "unauthorized", "message": "Missing, invalid or revoked API key." } }
Keep keys safe
- A key can read every site it's allowed to, so treat it like a password. Keep it on your server, not in browser code or a public repository.
- Give each service its own key, so you can revoke one without breaking the others.
- Use Only some sites when a service needs only a few sites.
- If a key may have leaked, revoke it in Settings β API access straight away and create a new one.
Last updated 2026-10-28