TSG GLOBAL/Developers
Campaign Manager Sandbox

Authentication & access

Use a company API key for REST or MCP. Staff integrations use explicit permissions and a selected company.

Sandbox environment

Brand and campaign submissions are simulated. Nothing reaches The Campaign Registry and no carrier charges are incurred. Use credentials issued for this environment.

Get a Campaign Manager key

Ask your TSG administrator for a partner API key assigned to your company. Authorized administrators issue keys in Companies → API Keys; the secret is shown once. If you do not see Companies, ask TSG to issue the key. You do not need access to that administration menu to use the API.

This key is distinct from TCR credentials, TNID account authorization, and keys for TSG’s messaging or number-management APIs. The same Campaign Manager key works for REST and operational MCP. Store it in your backend secret manager; do not put it in public browser code, URLs, source control, prompts, or logs.

Authenticate each request

Connection settings
Base URL: https://dev.10dlc-campaigns.com/api/v1
Authorization: Bearer <your-key>
Content-Type: application/json

X-API-Key is also accepted. Company partner and admin keys are bound to one company and must omit X-Company-Ref. Staff superadmin keys use explicit grants and must select an authorized company for business operations. See staff access for that setup.

Resource URLs use the opaque ref returned by the API. Save these refs with your own customer records. Integer IDs and TCR IDs are not interchangeable with Campaign Manager refs. A ref outside the selected company returns 404.

Access levels

Access levelAllowed actions
Partner (default)Create, scan, edit, verify, submit for review and read company records.
AdminPartner actions plus approval, resubmission, carrier-status reconciliation, deactivation and returning campaigns for revision. Still company-scoped.
Staff superadminExplicit permissions across an allowed set of companies, with a required target company, named active staff owner and expiration.

Admin credentials belong to trusted administrative backends. A partner's API key cannot approve its own submissions. Revoking a key stops both REST and MCP access.

Use the matching environment

Production and sandbox have separate credentials and records. This page’s environment label and base URL identify the target. A key issued for one environment is not a credential for the other. The neutral production API host is 10dlc-campaigns.com; the existing PhoneBurner host remains supported.