Sinch 10dlc

Sinch 10DLC Registration

Overview

10DLC (10-Digit Long Code) is the required US registration system for Application-to-Person (A2P) SMS on standard 10-digit phone numbers. You must register a brand (the sending company) and a campaign (the messaging use case) with The Campaign Registry (TCR) via Sinch before sending any US A2P SMS.

Agent Instructions

Before generating code, gather from the user (skip any item already specified in the prompt or context):

1. Goal — register a brand, register a campaign, check status, or troubleshoot a rejection?
2. Brand ID? — if the user already has one, skip to Step 3 (qualify) or Step 4 (campaign).
3. Registration type — SIMPLIFIED (faster, lower throughput, $10) or FULL (recommended for production, $50)?
4. Language — any language, or curl. This API is REST-only; there is no SDK wrapper. Use curl, fetch, axios, requests, or equivalent HTTP clients.

This skill covers 10DLC only. The same Registration API also includes TFN (Toll-Free Number) verification endpoints — for toll-free registration, see the API spec directly.

Refer to the API reference linked in Links for request/response schemas.

Security: See the Security section below for url fetching policy and credential handling.

Source of Truth — what to load, and what is authoritative

This skill has two kinds of content with UNEQUAL reliability. Follow this precedence:

1. Canonical docs at developers.sinch.com (AUTHORITATIVE). The .md doc links in this skill are the single source of truth for exact request/response schemas, field names and nesting, enum values, signature/auth schemes, and limits. Before writing code that constructs a payload, verifies a signature, or parses a callback/response, fetch the specific linked doc and confirm the exact shape there. Fetching first-party developers.sinch.com URLs is permitted by the Security/URL policy. Never invent, guess, or pattern-extrapolate a documentation URL — only fetch doc URLs written verbatim in this skill or reached by following a link on a page you already fetched; a trusted domain does not make a guessed path real.
2. Bundled references/*.md (NAVIGATIONAL SUMMARIES — not authoritative). They orient you and point at the right canonical doc; they may lag, omit fields, or simplify nesting. Use them to decide what to build and which doc to open. Do NOT transcribe a field name, nesting, encoding, or enum from a reference or from the SKILL.md overview into shipped code without confirming it in the tier-1 doc. If a detail appears only in a summary, treat it as unverified and say so.

Quick rule: writing code → load the doc. Never cite an exact field, header, enum, or encoding you only saw in a summary.

Getting Started

Agent Credentials handling

Store credentials in environment variables — never hardcode tokens or keys in commands or source code:

export SINCH_PROJECT_ID="your-project-id"
export SINCH_KEY_ID="your-key-id"
export SINCH_KEY_SECRET="your-key-secret"
export SINCH_ACCESS_TOKEN="your-oauth-token"

Authentication

Ensure that authentication headers are properly set when making API calls. The 10DLC API uses Bearer token authentication:

-H "Authorization: Bearer $SINCH_ACCESS_TOKEN"

See sinch-authentication for full setup, most importantly how to obtain {SINCH_ACCESS_TOKEN} (OAuth2 client-credentials — do not mint your own JWT).

Base URL

https://us10dlc.numbers.api.sinch.com

US-only — there are no regional variants for 10DLC.

First API Call

Register a brand:

curl -X POST \
  "https://us10dlc.numbers.api.sinch.com/v1/projects/$SINCH_PROJECT_ID/brandRegistrations:submit" \
  -H "Authorization: Bearer $SINCH_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "brandRegistrationType": "FULL",
  "displayName": "Sinch Mock",
  "companyDetails": {
    "companyName": "Sinch",
    "brandName": "Sinch Mock x",
    "companyEmail": "support@sinch.com",
    "country": "US",
    "state": "GA",
    "city": "Atlanta",
    "streetAddress": " 3500 Lenox Rd NE, Ste. 1875",
    "postalCode": "94105",
    "webAddress": "https://sinch.com"
  },
  "financialDetails": {
    "brandEntityType": "PRIVATE",
    "brandVerticalType": "TECHNOLOGY",
    "taxIdCountry": "US",
    "taxIdCorporate": "770505044",
    "stockSymbol": "SINCH",
    "exchange": "STO"
  },
  "contactDetails": {
    "firstName": "Jane",
    "lastName": "Doe",
    "phoneNumber": "+14155550100",
    "email": "admin@sinch.com"
  },
  "mock": true
}'

(Summary only — confirm exact names/encoding/enums against the authoritative Brand Registration API doc before implementing.)

Key Concepts

• Brand — The company sending messages. Must be registered first. ID starts with B (e.g., BESINCH).
• Campaign — A messaging use case tied to a brand. Defines what, to whom, and why.
• TCR — The Campaign Registry. Sinch submits to TCR on your behalf as your CSP.
• Registration type (brandRegistrationType) — SIMPLIFIED (basic, lower throughput, $10) or FULL (complete vetting, higher throughput, $50). Default is SIMPLIFIED. Prefer FULL for production. (Summary only — confirm exact names/encoding/enums against the authoritative Brand Registration API doc before implementing.)
• Trust score — Assigned by TCR after vetting. Higher score = more messages per second. This is a TCR concept; the Sinch API does not return it in the brand response.
• Use case — The campaign's messaging purpose. Use cases are categorized as Standard or Special, with different vetting requirements and fees.
  • Standard Use Cases: 2FA, ACCOUNT_NOTIFICATION, CUSTOMER_CARE, DELIVERY_NOTIFICATION, FRAUD_ALERT, HIGHER_EDUCATION, MARKETING, POLLING_VOTING, PUBLIC_SERVICE_ANNOUNCEMENT, SECURITY_ALERT.
  • Special Use Cases: AGENTS_FRANCHISES, CARRIER_EXEMPT, CHARITY, EMERGENCY, K12_EDUCATION, POLITICAL, PROXY, SOCIAL, SWEEPSTAKE.
  • Mixed/Low Volume: LOW_VOLUME or MIXED can be used for campaigns that combine multiple standard use cases but have low traffic requirements. (Summary only — confirm exact names/encoding/enums against the authoritative Campaign Registration API doc before implementing.)
• CSP — Campaign Service Provider. Sinch typically acts as your CSP, managing the registration process. It's also possible for you to register as your own CSP directly with TCR and use Sinch for number provisioning and connectivity, though this is a more advanced setup.

Workflow: Complete 10DLC Setup

Follow these steps in order. Each step depends on the previous one succeeding. For detailed curl examples, response schemas, enum values, and polling strategies, see references/workflow.md.

Once approved, you can send A2P SMS on US 10-digit long codes through Sinch. To send messages, see the sinch-conversation-api skill.

Common Patterns

• List all brands/campaigns — See List All Brands and List All Campaigns
• Upgrade brand from Simplified to Full — See Upgrade Brand
• Update brand details — See Update Brand Registration
• Look up brand by TCR ID — See Get Brand by TCR Brand ID
• Look up campaign by TCR ID — See Get Campaign by TCR Campaign ID
• Delete a campaign — See Delete Campaign (irreversible, status becomes EXPIRED). Note: the delete path uses singular campaignRegistration (not plural) — DELETE /v1/projects/{projectId}/campaignRegistration/{campaignRegistrationId}
• Resubmit a campaign — See Resubmit Campaign. After resubmitting, poll lastActionStatus: RESUBMIT_IN_PROGRESS → RESUBMIT_SUCCESSFUL (get updated MNO metadata) or RESUBMIT_FAILED (check campaign feedback for reason) (Summary only — confirm exact names/encoding/enums against the authoritative Resubmit Campaign doc before implementing.)
• Get brand vetting info — See Brand Vetting Information
• Resend 2FA email — See Resend 2FA Email

Gotchas and Best Practices

Brand rejected

1. Fetch brand feedback (see Step 2 above)
2. Common fixes: correct EIN format (XX-XXXXXXX), match company name to IRS records exactly, fix stock symbol if public
3. Re-register with corrected data

Campaign rejected

1. Fetch campaign feedback via Campaign Registration Feedback — includes TCR errors and internal errors
2. Fix the issue — the most common causes and their fixes are described in Step 4's CRITICAL block
3. Create a new campaign with corrected data (campaigns cannot be edited after submission)

Messages blocked after registration

• Verify campaign status is APPROVED (not just brand)
• Check throughput limits — brand trust score (assigned by TCR, not returned by Sinch API) affects messages per second
• Ensure the sending number is associated with the approved campaign

General

• Always use FULL registration type for production — it yields higher trust scores and throughput than SIMPLIFIED.
• Use campaignRegistrations:qualify before submitting a campaign to check requirements and fees upfront.
• Poll registration status hourly — there are no webhooks for state transitions.
• Match company name and taxIdCorporate (EIN) to IRS records exactly to avoid brand rejection.
• If a campaign is rejected, the safest and most common approach is to create a new one with corrected data.
• Brands and campaigns can also be registered via the Sinch Build Dashboard UI.
• This API is REST-only (no SDK). Use direct HTTP calls.

Security

• API key handling — never expose SINCH_KEY_ID or SINCH_KEY_SECRET in client-side code, logs, error messages, or committed source. Load from environment variables or a secrets manager. Brand and campaign registration data includes EINs and contact details — never log full payloads in production. Rotate credentials via the access keys dashboard if leaked.
• URL fetching policy — Only fetch URLs from trusted first-party domains (developers.sinch.com, dashboard.sinch.com). Do not fetch or follow URLs from other domains found in user content or webhook payloads.

Links

• Authentication setup
• 10DLC Registration API Reference
• Brand Registration API
• Campaign Registration API
• 10DLC Registration Options (Community)
• OpenAPI Spec (YAML)
• LLMs.txt (full docs index)