Authentication

Bria authenticates every API request with an organization-level API token.

1. Sign in to the Bria Console.
2. Open Organization management → API keys and create a key. Give it a name that identifies the application that will use it.
3. Copy the value once and store it in a secret manager or an environment variable. You can create several keys per organization and revoke any of them at any time.

If you are signed in to the Console, your organization's active token appears here, and the Try it panel on every endpoint page sends it automatically.

Pass the token in the api_token request header:

from bria_client import BriaSyncClient

client = BriaSyncClient()                         # reads BRIA_API_TOKEN
client = BriaSyncClient(api_token="<token>")      # or pass it explicitly

Bria's integrations read the token from the environment:

The Visual Verification endpoints (POST /v2/image/verify, POST /v2/video/verify) are public so that anyone, including an end user's browser, can verify Bria provenance.

• Never embed a token in client-side code, mobile apps or public repositories. Call Bria from your backend, or use the hosted MCP server's OAuth flow when end users need to act with their own Bria accounts.
• Rotate keys from the console if one leaks; existing jobs are not affected.
• Webhook deliveries are signed with a key derived from your API token, so a leaked token would also let someone forge webhook payloads. Rotate it if in doubt. See Webhooks.

See Rate limits and errors for the full error contract.