Brand Identity API
Registering a brand’s trust posture is normally scattered across six unrelated flows — a 10DLC brand + campaign, a toll-free verification, a WhatsApp Business verification, an RCS agent verification, branded calling (RCD/CNAM), and per-number regulatory KYC. Brand Identity doesn’t replace any of those registration flows; it reads the current status of each one and rolls them into a single trust score plus a prioritized list of what to do next, so a tenant can see “how verified am I, everywhere” at a glance instead of checking six settings pages. Base path:/api/v1/brand-identity
Authentication: API key (X-API-Key) or session JWT. Any authenticated role (owner, admin, developer, viewer) can read the status.
Channels covered
Each channel is scored independently, then combined into the overall posture:
Each channel reports one of five states:
not_started, in_progress, verified, action_required, or unavailable (the underlying subsystem couldn’t be reached this call — it degrades that one channel rather than failing the whole response).
Response shape
trustScore is verified / applicable (rounded to an integer 0–100); a channel in unavailable doesn’t count against the score. nextActions is sorted so the highest-priority gaps (urgent before todo) appear first — this is what the dashboard’s brand-trust widget renders directly.
See also
- Brand identity & trust score concept — what the score means and how to run it in ops
- 10DLC registration guide — register the 10DLC brand this endpoint reads status from
- WhatsApp Business setup
- Numbers → regulatory preview
- Compliance → sender-ID registration