For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SupportDashboard
DocsAPI ReferenceWebhooksMethodsUI ComponentsMCP ServerChangelog
  • Documentation
    • Introduction
    • Authentication
    • RCS Support
  • Quickstart
    • SMS
    • RCS
  • Guides
    • Purchase Phone Numbers
    • Brands
    • Campaigns
    • Messages
    • Branded Test Agents
    • Handling Expired URLs
LogoLogo
SupportDashboard
On this page
  • Prerequisites
  • Step 1: Create or update the brand
  • Step 2: Submit for verification
  • Step 3: Monitor and refresh status
Guides

Register Your Brand

Was this page helpful?
Previous

Campaigns Overview

Next
Built with

Carriers check your brand before they approve any campaign. Register it once and reuse the resulting brandId across 10DLC, Toll-Free, and RCS flows.

⏱️ Approval time: Less than 15 minutes

Prerequisites

  • Legal entity name (and DBA if applicable) plus a website that matches public records
  • Federal EIN or Tax ID, business address, and a reachable support contact
  • Vertical, use case, and opt-in details that carriers can audit later

Step 1: Create or update the brand

  • Upsert the record with POST /brands. Re-send the request with specific fields whenever you need to fix data before submission.
  • Call the optional helpers:
Optional helpers

  • POST /brands/autofill uses the brand name, website, and/or additional info to fill in the brand information.

  • POST /brands/validate checks for common formatting and brand issues. Treat the response as advisory feedback — we surface major concerns but never block submission.

Step 2: Submit for verification

  • Push the profile for review with POST /brands/{brandId}/submit.
  • Request additional vetting for higher throughput with POST /brands/{brandId}/vet.
  • Standard verification completes in under 15 minutes; optional vetting typically finishes within one to three business days.

Step 3: Monitor and refresh status

  • Retrieve the full record with GET /brands/{id} whenever you need the latest carrier response.
  • Force a status refresh through GET /status/brand/{brandId}.