Campaign Manager API & MCP
On this page
Use Campaign Manager to register customer brands, prepare messaging campaigns, submit them for TSG review, and follow the recorded outcome. The REST API and operational MCP server share company permissions and workflow rules.
Documentation and environments
| Resource | URL |
|---|---|
| Developer guides | Campaign Manager documentation |
| Interactive API reference | Requests, schemas, and responses |
| OpenAPI specification | Campaign Manager OpenAPI JSON |
| Production REST base URL | https://10dlc-campaigns.com/api/v1 |
| Production operational MCP | https://10dlc-campaigns.com/api/v1/mcp |
| Sandbox developer guides | Campaign Manager sandbox |
The linked Campaign Manager specification is the authoritative operation catalog for that product. It is separate from the SMS, MMS, and number-configuration OpenAPI document in this documentation hub. The existing PhoneBurner API host remains supported; new partner integrations should use the neutral 10dlc-campaigns.com host.
Authentication and company scope
Ask your TSG administrator for a Campaign Manager partner API key assigned to your company. Send it on every request:
Authorization: Bearer <campaign-manager-api-key>
This is a separate credential from your messaging API key, Customer Portal login token, TCR credentials, and TNID account authorization. Keep it in a secret manager. Do not put it in public frontend code, URLs, prompts, or logs.
Company partner and admin keys are bound to one company and must omit X-Company-Ref. Staff superadmin keys require explicit permissions and an authorized company target. See authentication and staff access.
Production and sandbox use separate credentials and records. The Campaign Manager sandbox simulates registry submissions; production registration and submission actions can affect live services and incur charges.
Discover brands and campaigns
Start with a read-only request. Load your key into TSG_API_KEY through your backend secret manager:
curl --get "https://10dlc-campaigns.com/api/v1/brands" \
-H "Authorization: Bearer $TSG_API_KEY" \
--data-urlencode "limit=25"
curl --get "https://10dlc-campaigns.com/api/v1/campaigns" \
-H "Authorization: Bearer $TSG_API_KEY" \
--data-urlencode "limit=25"
Results appear in data.brands or data.campaigns. Each record includes an opaque ref; use it with GET /brands/{ref} or GET /campaigns/{ref}. Campaign Manager refs are not TCR IDs or numeric database IDs.
Follow data.next_cursor by passing it unchanged as cursor on the next request. Stop when it is null. limit defaults to 25 and accepts 1–100. Campaign lists optionally accept brand_ref; keep the same filter on every page. Cursors are bound to the company, list, and filter. See lists and pagination.
Lists contain records already stored in Campaign Manager. Campaigns submitted directly to TCR appear after a separate authorized import. These list requests do not fetch or import TCR records.
Connect the operational MCP server
| Setting | Value |
|---|---|
| Endpoint | https://10dlc-campaigns.com/api/v1/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer <campaign-manager-api-key> |
| Credential | The same company-scoped key used for Campaign Manager REST |
Use a client that supports custom authorization headers and secure credential settings. This server has no OAuth sign-in flow. It accepts MCP messages through POST; opening the endpoint in a browser sends GET and returns 405.
Discover the available tools with tools/list. Start with the read-only list_brands and list_campaigns tools. Both accept limit and cursor; list_campaigns also accepts brand_ref. The tool response contains the REST envelope under structuredContent; follow structuredContent.data.next_cursor for subsequent pages.
Other tools can create or change records and initiate workflow actions. Availability depends on permissions and enabled features. Inspect the discovered schema and results rather than assuming that an HTTP 200 means the business action succeeded. See the complete MCP setup and troubleshooting guide.
Documentation MCP versus operational MCP
The public documentation MCP server searches and reads these docs without an API key. It cannot read your private records or operate on campaigns. Do not send your Campaign Manager key to the documentation server.
The authenticated Campaign Manager server described above operates within your API key’s permissions. These are separate services, even though both use MCP.
Choose a registration workflow
- Standard businesses: website scan, reviewed business details, and identity verification.
- Sole proprietors: direct brand creation and YES-reply SMS verification.
- Campaigns and review: editable AI drafts or supplied content, review, revisions, and recorded status.
- Managed onboarding: authorized TNID connections and account-specific reseller workflows.
- Business applications: import existing EIN-business facts while preserving the source application.
- Customer assistance: inquiries, exact-version prepared reviews, and actual expedite quotes.
Internal review, upstream submission, carrier approval, and activation are separate outcomes. The feature-gated /registrations foundation for toll-free, short code, and RCS does not provide a live provider adapter; check registration capabilities before using it. Existing TSG GraphQL compliance order forms are a separate interface.
Errors and retries
Read error.code, error.message, and optional error.details in REST responses. MCP business errors set isError: true and include error.http_status in the structured response. Credentials, scopes, and business-state errors require different handling.
Use backoff for status polling. Only reuse an idempotency key for the same supported operation and unchanged request body. Do not blindly repeat a create or submit request after an ambiguous timeout. See errors, limits, and retries.