Bandwidth is retiring legacy Campaign Management APIs and UI and moving all 10DLC brand and campaign registrations to the new and improved 10DLCRegistration Center. Here is everything you need to plan your transition based on how you manage your migration today.
Important First Step: Account migration requires Bandwidth enablement. Please open a support ticket to get started. Account enablement typically takes about a week.
Key Retirement Deadlines
Note: Active brands and campaigns created before these dates will continue working without interruption.
Campaign Type | Legacy End Date | Impact on Legacy Endpoints
|
Direct Campaigns & Brands | January 21, 2027 | Cannot create new 10DLC brands or campaigns
|
Imported Campaigns | August 1, 2027 | Cannot import new 10DLC campaigns
|
Why Move? Key Benefits
Dashboard Cleanup: You’ll now be able to hide expired campaigns.
Better Tracking: Direct phone-number-to-campaign mapping, full 10DLC number history, and a view of all registered phone numbers on your account.
Enhanced Search: Rich multi-attribute filtering and sorting across both UI and API.
Future-Ready: Centralized profile data built to support future messaging channels.
Path 1: UI-Only Migration
If you manage brands and campaigns exclusively through the Bandwidth portal, your migration requires zero code changes. Bandwidth moves your account behind the scenes, and what changes is simply where and how you register afterward.
Your Migration Steps
Contact Bandwidth: Open a ticket or reach out to your Account Manager to request enablement.
Wait for Confirmation: Enablement is usually complete within one week.
Start Using the Registration Center: Register all new brands and campaigns in the new portal moving forward.
What to Review After Migration
Updated Registration Workflows: Review guidelines for registering, importing, and moving campaigns, and how to register brands in the registration center.
User Roles: Confirm team members have the Campaign management, Configuration, and Credential access roles.
Auth+ Requirements: Check required verification details for your brand entity types.
Path 2: API Integration Migration
If you create or manage brands and campaigns using our API, this migration requires code updates. The new v2 API uses JSON instead of XML, updates endpoint base paths, and transitions processing to asynchronous execution.
Before You Begin
Download the attached Campaign Management API Comparison (v1 vs v2) PDF.
Review the new A2P Campaign Management (10DLC) API Documentation.
Locate all internal scripts, tools, and services calling legacy campaignManagement/ endpoints.
Ensure your API users hold the Campaign management, Configuration, and Credential access roles. If you do not have this level of access please reach out to your Bandwidth Account team.
Your Migration Steps
Contact Bandwidth using the steps above. To coordinate timing with you so your code and your account switch together. Note that currently all migrations are done on Tuesdays.
Update your integration to the new endpoints for brand and campaign provisioning.
Update your Brand Vetting workflows to use the new vetting endpoints.
Update internal tools and scripts that point to the legacy campaignManagement/ base URL.
Confirm your changeover date with us. We enable your account on the agreed date.
Subscribe to Release Notes to hear about new API features and changes.
API Differences at a Glance (v1 vs. v2)
For a full, field-by-field endpoint mapping, refer to the attached API Comparison PDF. Campaign Management API Comparison.pdf
Feature | Legacy (v1) | New (v2)
|
Payload Format | XML | JSON |
Execution Mode | Synchronous | Asynchronous |
Identifiers | Bandwidth IDs only | Interchangeable Bandwidth & TCR IDs |
Campaign Endpoint | /api/v1/.../campaignManagement/10dlc | /api/v2/.../tendlc/campaigns |
Brand Endpoint | /api/v1/.../campaignManagement/10dlc/brands | /api/v2/.../tendlc/brands |
Pagination & Sorting | page / size (basic sort) | offset / limit (multi-field sort) |
Auth & Number Assigning | Basic Auth / POST /tnoptions | No change (Basic Auth / POST /tnoptions) |
New Feature: Customer Profiles
The v2 API introduces Customer Profiles to group business entity details behind your brands:
Map each brand to a single reusable organization profile.
Search, filter, and view version history using /accounts/{accountId}/customerProfiles.
Manage profile lifecycles with soft-delete support.
Auth+ Verification Requirements
If you are utilizing Bandwidth directly for your campaign management please note that new campaigns require active Auth+ verification for associated brands before launch:
Brand Entity Type | Auth+ Mandate Date
|
PUBLIC_PROFIT | Required now |
GOVERNMENT | Required starting January 21, 2027 |
NON_PROFIT & PRIVATE_PROFIT | Optional until April 29, 2027 (Required thereafter) |
What Stays the Same
Active brands and campaigns created before retirement dates keep working without disruption.
API credentials and Basic Authentication methods stay identical.
Assigning campaigns to phone numbers using TN Option Orders works the same way.
Need Help?
Open a ticket with the Bandwidth support team. We are here to help you move smoothly to the Registration Center!