# A2P 10DLC · Brand and campaign registration for US SMS The brand, campaign and number 01 · Brand Identify the legal business behind the traffic. 02 · Campaign Declare the use case, content and consent flow. 03 · Number Link the number to an approved campaign. Before sending Enable the destination and check current eligibility. A conceptual registration workflow. Carrier and registry review determine the actual status. ## Why 10DLC exists. A2P 10DLC is part of [SMS compliance](/sms-api/features/compliance) on the [Bird SMS API](/sms-api). US carriers require any business sending application traffic over local long codes to register the brand behind it and each campaign it runs. Registered traffic earns vetted throughput and carrier trust; unregistered traffic gets filtered. Bird files both and reports approval state so you send into a campaign that's actually live. ## The registration flow. Brand, then campaign, then the numbers that carry it. - **01** Register a brand. Submit the legal entity behind your traffic. The carriers vet it and the brand becomes the identity every campaign attaches to. - **02** Register a campaign. Describe the messages you send: the use case, sample content, and opt-in flow. Approval is what unlocks the campaign's throughput. - **03** Associate your numbers. Attach the long codes that will carry the campaign. From then on their US application traffic runs over the registered campaign. - **04** Query status until it's live. Review the registry status and any requested corrections. Link the number only after the campaign is approved, and enable the destination before sending. ## Check a campaign's status from the API. Read the requirements, prepare the brand and campaign, then inspect their status in Bird. Read the campaign by its ID and wait for approval before linking a number for traffic. **campaign-status.ts** ```typescript // The 10DLC surface is not on the SDK yet, so read it over HTTP with a key // carrying the sms_management:read scope. const res = await fetch( `https://eu1.platform.bird.com/v1/sms/10dlc/campaigns/${campaignId}`, { headers: { Authorization: `Bearer ${process.env.BIRD_API_KEY!}` } }, ); const campaign = await res.json(); if (campaign.status === "approved") { // throughput is live — safe to send } console.log(campaign.brand_id); // → "brd_01krdgeqcxet5s7t44vh8rt9mg" ``` ## 10DLC is how long codes earn US throughput. If you send from [long codes](/sms-api/features/numbers/long-codes), 10DLC is what turns them from a filtering risk into a vetted sender. The number is yours the moment you buy it, but its US application traffic only flows at full rate once the campaign it's associated with is approved. ## What registration costs. Review the published registration fees before submission. Brand registration, campaign vetting and recurring campaign charges have separate prices in the [Bird pricing catalogue](/pricing/sms/fees). A corrected resubmission can be a new chargeable attempt. ## Questions about registration and sending ### What is the brand, campaign and number model? The brand identifies the business. A campaign declares a use case under that brand. Link the sending numbers to an approved campaign before using them for US application-to-person traffic. ### Can I change a campaign’s use case? The registered use case cannot be changed. Prepare a new campaign when the use case changes, and review the requirements and charges before submitting. ### Does brand approval mean the number can send? No. Complete campaign approval, link the number and enable the destination. A public-company brand also has an Auth+ requirement before campaign registration. ### Does 10DLC apply to toll-free numbers? Toll-free messaging follows its own verification program. 10DLC applies to US long-code application-to-person messaging. ## Other compliance topics 10DLC is one of three SMS compliance regimes. See the rest. - [Opt-out and keywords](/sms-api/features/compliance/opt-out): Supported keyword handling and a queryable sender-and-subscriber suppression list. - [Sender-ID registration](/sms-api/features/compliance/sender-id-registration): Pre-register alphanumeric sender IDs where countries require it. - [All SMS compliance](/sms-api/features/compliance): 10DLC, opt-out, and sender-ID registration in one place. - [SMS API overview](/sms-api): The full SMS API: sending, numbers, two-way, compliance, routing, and analytics. ## Scale without losing control. Organize teams in workspaces, control API access, and trace changes through audit logs. Harbor Organization Workspaces Production Sandbox ### Delivery agent API key · Customer operations team Active Permissions Access Email Read & write SMS Read & write WhatsApp Read Read & write AL Alex Lee Admin Permissions updated ### Audit log Production API key updated Alex Lee · 09:42:18 UTC Workspace Production Resource Delivery agent WhatsApp Read Read & write Succeeded [Workspaces](/docs/guides/workspaces)[Team roles](/docs/guides/users-teams-roles)[API authentication](/docs/guides/authentication) [Explore Enterprise](/enterprise) ## Start with SMS. Build across channels with Bird. [Get started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fonboarding) · [Contact Sales](/demo?product=sms) [Email](/email-api) · [SMS](/sms-api) · [WhatsApp](/whatsapp-api) · [Apple Messages](/apple-messages-api) · [Voice](/voice-api) ## Related resources - [Registering your SMS sender ID](/learn/sms/registering-your-sms-sender-id) (video) - [SMS sender IDs](/docs/guides/sms/senders) (docs) - [What is sender ID registration, and why do some countries require it?](/explained/sms/what-is-sender-id-registration) (answer) - [Build your first integration](/learn/paths/integration) (course) [Get an implementation brief](/learn/workspace?topic=sms-senders)