Authentication

Every request needs one of your account's API keys.

Make a key

1. Open Dashboard › API.
2. Give the key a name that says where it's used, like "Website server".
3. Choose Make key, then copy the key.

The key shows only once. SiteBrite keeps a fingerprint of it, not the key, so it can't be shown again. If you lose it, revoke it and make another.

• Who can make keys: the account's owners and developers. Editors can't, since a key can spend the account's credits.
• Which accounts: any account with a plan (a website plan or Studio) or with credits.
• How many: up to 20 at once.
• What a key reaches: everything in the account: all of its brands, its minutes and its credits.

Send it

Send the key in the Authorization header of every request:

curl https://sitebrite.app/api/v1/brands \
  -H "Authorization: Bearer sbk_your_key_here"

Keys start with sbk_. A missing, wrong or revoked key gets a 401.

Keep it secret

• Keep the key on your server, in an environment variable or a secrets store. Never commit it to code.
• Never send it to a browser or put it in an app. The API doesn't answer requests from web pages for this reason.
• Make one key for each place that uses the API. Then you can revoke one without stopping the others.

Revoke a key

In Dashboard › API, choose Revoke next to the key. It stops working at once. Videos it already made stay.

An address that keeps sending wrong keys is blocked for an hour. See Errors and limits.