APIs · Authentication

One key. Standard bearer header.

Every REST endpoint accepts a personal API key sent as a bearer token. Each key belongs to one workspace. Mint your first key once in the dashboard; every key after that can be minted, listed and revoked over the API.

Mint a key

  1. Open /dashboard/developer in your browser and sign in.
  2. Under REST API keys, click Mint key. Name it something you'll recognise (“cron”, “n8n”, “airflow”).
  3. Copy the shown bm_live_... value immediately. We don't store the plaintext, so you can't view it again. If you lose it, revoke and mint a new one.

From then on, use POST /account/api-keys to mint a key per client workspace or per integration.

Send it

Add an Authorization header on every request:

curl https://api.brandmov.com/api/v1/watchlists/ \
  -H "Authorization: Bearer bm_live_your_key_here"

All endpoints live under https://api.brandmov.com/api/v1. Send JSON when a body is required.

A key acts on the workspace it was minted in. Add X-Workspace-Id: <id> to act on another workspace you belong to. GET /account/workspaces lists them. See Account & workspaces.

Errors

Missing or malformed header: 401 Unauthorized.

{
  "detail": "Not authenticated"
}

Valid key but your plan doesn't include REST API access (Tier 2 and up qualify): 403 Forbidden.

{
  "detail": "REST API access is not enabled for your plan"
}

Key minted in a workspace that has since been archived: 403 workspace_archived. Send X-Workspace-Id for another workspace, or restore it with POST /account/workspaces/{id}/unarchive.

Rotate & revoke

DELETE /account/api-keys/{id}, or click Revoke on the dashboard page. Revocation is immediate: the next request that uses the key returns 401. For zero-downtime rotation, mint the new key first, switch over, then revoke the old one.