Skip to main content
Use one approved Rainbrand account to own the integration. Sign in with that account, then create a dedicated API key in Account. Brand Skills belong to the account behind the key, so keep the integration on that account when rotating keys. Rainbrand shows a new key once. Store it on your server and never expose it in browser code, logs, source control, or agent prompts. Keys start with bloom_sk_, the prefix from Rainbrand’s former name. Store it in your backend’s secret manager:

​
Send the key

Use x-api-key unless your HTTP client requires a bearer token:
Both headers authenticate the same key. Do not send both.

​
Base URL

All Brand Skill endpoints use the production base URL:
If a key may have been exposed, revoke it in Account and create a replacement from the same account. See the API reference for the exact authentication and access errors.