Register for 10DLC texting
US carriers require every business that texts from a local 10-digit number (a "10DLC" number) to register. Unregistered texts are filtered or blocked. In this guide, you will register a brand (a business identity), register a campaign (what you send, and how people agree to receive it), and put your Resia numbers on that campaign. If you text for several businesses, register one brand for each business, then campaigns under each brand. Each number goes on one campaign, so its texts go out under that campaign's brand.
A brand costs the registry's one-time brand fee when it is registered. A campaign costs one month when the registry accepts it, then one month on the same day of each later month until you release it. If the registry rejects a campaign, Resia charges a one-time rejection fee and no later month. Charges come from your prepaid balance and are not refundable.
Sole proprietors and publicly traded companies cannot register through the API yet. Contact support@resia.ai. Contact support also if you already registered a brand somewhere else.
Before you start
- Complete Get access. Keep that terminal open, with
RESIA_API_BASEandRESIA_API_KEYset. - Your company's registered details: legal name, EIN, address, website, and a public privacy policy page.
- A prepaid balance above $0.00. See Billing.
- A Resia number to send from. See Buy a phone number.
- Write every phone number in E.164 form, such as
+12125550142. See Number format.
Register a brand
The brand is the legal business behind the texts. Register one brand for each business that you text for: each brand needs that business's own legal name and tax ID. The registry checks the details against public records, so enter them exactly as your company is registered.
You can also register the brand with a form in the portal. Open Numbers, select the 10DLC Campaigns tab, and select Register brand.

With the API:
cat > brand.json <<'JSON'
{
"entity_type": "PRIVATE_PROFIT",
"display_name": "Midtown Eye Care",
"company_name": "Midtown Eye Care LLC",
"ein": "12-3456789",
"street": "100 W 40th St",
"city": "New York",
"state": "NY",
"postal_code": "10018",
"country": "US",
"email": "office@midtowneyecare.example",
"business_phone": "+12125550100",
"vertical": "HEALTHCARE",
"website": "https://midtowneyecare.example"
}
JSON
BRAND_REQUEST_KEY=$(uuidgen)
curl --fail-with-body --silent --show-error \
"$RESIA_API_BASE/v1/10dlc/brands" \
--header "Authorization: Bearer $RESIA_API_KEY" \
--header 'Content-Type: application/json' \
--header "Idempotency-Key: $BRAND_REQUEST_KEY" \
--data-binary @brand.json
entity_typeisPRIVATE_PROFIT,NON_PROFIT, orGOVERNMENT.- The answer carries
brand_id, the brand's Telnyx brand ID. Keep it: campaign requests name the brand with it when you have two or more brands. - Resia charges the registry's one-time brand fee when the brand is registered. It is not refunded. A balance of $0.00 or less gets
402. Idempotency-Keyis optional. With a key, run the same command again after a failure or a timeout: Resia returns the original brand and never registers or charges twice. Without a key, each request registers a new brand.- If the outcome is unknown, the brand appears in
GET /v1/10dlc/brandsonce the registry shows it.
List your brands, with each brand's names and verification, with GET /v1/10dlc/brands. Verification usually finishes within minutes, but it can take days.
POST /v1/10dlc/brand and GET /v1/10dlc/brand are deprecated. They work for one brand only: the first answers 409 once you have a brand, and the second answers 409 once you have two.
API reference: Register a brand and List your brands.
Register a campaign
First, list the campaign types that the brand qualifies for, with Resia's monthly price. With two or more brands, name the brand with brand_id; without it, the answer is 422:
read -r -p 'Brand id (brand_id from GET /v1/10dlc/brands): ' BRAND_ID
curl --fail-with-body --silent --show-error --get \
"$RESIA_API_BASE/v1/10dlc/campaign-use-cases" \
--data-urlencode "brand_id=$BRAND_ID" \
--header "Authorization: Bearer $RESIA_API_KEY"
Each use case has a monthly_fee. This is what Resia charges for one month of the campaign. Copy it into confirmed_upfront_fee when you register. If the price changed, Resia charges nothing and answers 409. quarterly_fee and annual_fee are the registry's own fees, for reference only.
cat > campaign.json <<'JSON'
{
"usecase": "CUSTOMER_CARE",
"description": "Appointment reminders and replies to patient questions for Midtown Eye Care.",
"sample_messages": [
"Midtown Eye Care: your appointment is tomorrow at 3:30 PM. Reply C to confirm or STOP to opt out.",
"Midtown Eye Care: thanks, your appointment is confirmed. Reply HELP for help or STOP to opt out."
],
"message_flow": "Patients give their mobile number and check an unticked consent box on the booking form at https://midtowneyecare.example/book. The box says they agree to receive appointment texts, that message and data rates may apply, and that they can reply STOP to opt out.",
"help_message": "Midtown Eye Care: for help call +12125550100. Reply STOP to opt out.",
"optout_message": "Midtown Eye Care: you are unsubscribed and will get no more texts.",
"privacy_policy_link": "https://midtowneyecare.example/privacy",
"terms_and_conditions_link": "https://midtowneyecare.example/sms-terms",
"confirmed_upfront_fee": "20.00",
"brand_id": "4b20019f-c8f8-b137-11ae-15a79b2aa562"
}
JSON
CAMPAIGN_REQUEST_KEY=$(uuidgen)
curl --fail-with-body --silent --show-error \
"$RESIA_API_BASE/v1/10dlc/campaigns" \
--header "Authorization: Bearer $RESIA_API_KEY" \
--header 'Content-Type: application/json' \
--header "Idempotency-Key: $CAMPAIGN_REQUEST_KEY" \
--data-binary @campaign.json \
--output campaign-response.json
- Replace
20.00with themonthly_feefrom the listing. - Replace
brand_idwith the brand that the campaign is for. With one brand, you can leavebrand_idout. - A balance of $0.00 or less gets
402, and Resia charges nothing. - Some use cases, such as
LOW_VOLUMEandMIXED, also needsub_usecases: the standard categories that your texts really are, such as["ACCOUNT_NOTIFICATION", "CUSTOMER_CARE"]. Each use case in the listing hasmin_sub_usecasesandmax_sub_usecases. When the minimum is above0,sub_usecasesis required. The list holds at most 5 entries. A count outside the bounds gets409, and Resia charges nothing. Idempotency-Keyis optional, but use it. If the request fails or times out, run the samecurlcommand again. It reusesCAMPAIGN_REQUEST_KEY, so Resia returns the original registration and never charges twice. Without a key, each request is a new submission, so a retry can register and charge twice.- Registry and carrier review take hours to days. Follow it with
GET /v1/10dlc/campaigns/{campaign_id}. - Resia charges the first month when the registry accepts the submission. A campaign that is suspended or expired on its monthly date costs nothing for that month.
Campaign status is pending review, active, rejected, suspended, or expired. Only an active campaign delivers texts.
Release a campaign
To stop a campaign and its monthly charges, release it:
curl --fail-with-body --silent --show-error --request DELETE \
"$RESIA_API_BASE/v1/10dlc/campaigns/$CAMPAIGN_ID" \
--header "Authorization: Bearer $RESIA_API_KEY"
- Resia detaches the campaign's numbers, and the registry ends the campaign. Your numbers stay yours, but they cannot send business texts until you put them on another active campaign.
- Release cannot be undone. The month already charged is not refunded.
- Only a campaign that you registered through Resia can be released. Any other campaign gets
404. If the registry fails, the campaign is not released and its charges continue, but numbers detached before the failure stay detached. Run the command again to finish.
In the portal: open Numbers, select the 10DLC Campaigns tab, and select Register campaign.
An unclear consent description is a common reason for rejection. Make message_flow describe exactly how a person agrees to receive texts, and make sure the privacy policy and terms pages are public and mention text messages.
API reference: See what you can register, Register a campaign, and Read one campaign.
Put your numbers on the campaign
When the campaign is active, attach each number that will send for it:
read -r -p 'Campaign id: ' CAMPAIGN_ID
curl --fail-with-body --silent --show-error \
"$RESIA_API_BASE/v1/10dlc/campaigns/$CAMPAIGN_ID/phone-numbers" \
--header "Authorization: Bearer $RESIA_API_KEY" \
--header 'Content-Type: application/json' \
--data '{"phone_number": "+12125550199"}'
Resia answers 202. Carriers finish setting up the number in the background, usually within a couple of hours. Check progress with GET /v1/10dlc/campaigns/{campaign_id}/phone-numbers.
To put a new number on a campaign when you buy it, add campaign_id to POST /v1/phone-number-orders. Resia attaches the number when the purchase completes. A campaign without a number pool takes at most 49 numbers through an order; a full campaign answers 409. See Buy a phone number.
A number can be on only one campaign at a time. To move a number to another brand's campaign, take it off its campaign first, then attach it:
curl --fail-with-body --silent --show-error --request DELETE \
"$RESIA_API_BASE/v1/10dlc/campaigns/$CAMPAIGN_ID/phone-numbers/%2B12125550199" \
--header "Authorization: Bearer $RESIA_API_KEY"
- Resia answers
204. A number on no campaign also gets204, and nothing changes. A number on a different campaign gets409, and nothing changes. - Until the number is on an active campaign again, its business texts fail.
Each brand has its own opt-out list. When a person texts STOP to a number on a campaign of one brand, that brand's texts to the person stop. A number belongs to a brand only after Resia attached it to that brand's campaign. A number with no brand also stops sending to that person. This covers a number on no campaign, a number on a campaign that Resia shares with you, a number attached outside Resia, and a number that was on a campaign before brands existed until its brand's next number is attached. A STOP to a number with no brand stops every text of your organization to that person.
In the portal: select Manage next to the number. In its 10DLC campaign section, choose the active campaign and select Assign.
API reference: Put a number on a campaign, Take a number off a campaign, and See which numbers are on a campaign.
In the portal
Open Numbers and select the 10DLC Campaigns tab. It shows your brand and its verification, and lists your campaigns with their type and state.
- Register campaign opens a form. Choose the Campaign type, fill in the fields, and confirm the monthly charge. When the type needs
sub_usecases, the form shows Sub-types with the number to choose. - Select a campaign to see its Campaign status and its Assigned numbers with each number's carrier state. Select Check again to read the status again.
- To put a number on a campaign, select Manage next to the number on the Phone Numbers tab. In the number's 10DLC campaign section, choose the active campaign and select Assign.
A Chat Agent cannot be assigned to a number until the number is on an active campaign. The number's page says why the choice is locked. See Phone numbers.
If something fails
409when you register a campaign: the monthly price changed, or thesub_usecasescount is outside the bounds. Resia charges nothing. Read the listing again and resend.422with "Name one with brand_id": your organization has two or more brands. Addbrand_idto the request.- A campaign is
rejected: the registry or a carrier refused it, often because of an unclear consent description. Fixmessage_flowand the linked pages, then register again. Resia charges the rejection fee once; the first month is not refunded. 422when you assign a Chat Agent to the number: the number is notASSIGNEDon an active campaign yet. Wait for the carrier, then retry.- A text fails with
sender_not_registered: the sending number is not on an active campaign. Put it on one, then send again.
Next steps
- Send text messages in bulk: one-way texts from the registered number.
- Answer texts to your number: answer texts to the registered number.

