Developers

Brand Engine API

Brand identity is compiled once in the hub and read everywhere else. This API is how your services and federated tools fetch it, stay in sync, and send events back.

Quickstart

From zero to a cached brand bundle in four steps.

  1. 1. Get a credential. For your own back-office services, issue an API key (be_…) from the Developer page inside the hub. For a federated child tool, ask the hub owner for CORE_CHILD_APP_TOKEN__<TOOL> and CHILD_WEBHOOK_SECRET__<TOOL>.
  2. 2. Confirm access. Call GET /api/public/brands with the API key. You should get back the brand the key is scoped to, including its current identity_version.
  3. 3. Read the identity. From your backend call GET /api/public/v1/brand/by-id/:id/bundle with the child token and X-Tool-Slug header. Store the response in a brand_cache row keyed by brand_id, together with identity_version.
  4. 4. Stay fresh. Expose a webhook endpoint, verify X-Hub-Signature with CHILD_WEBHOOK_SECRET__<TOOL>, and mark the matching brand_cache row stale on identity.updated. Re-fetch the bundle with ?since=<cached version> on the next read.

First call

curl https://thebrandengine.ai/api/public/brands \
  -H "Authorization: Bearer be_xxxxxxxxxxxxxxxx"

v0 public API

Bearer API key or user session token. For your own services, webhooks, and automations.

v1 ecosystem contract

Server-to-server endpoints used by federated tools such as Dialog Center and AI Agents.

Other formats

The HTML reference is the source of truth. These are generated from it.