Update A2P Registration
Update an existing A2P 10DLC registration.
Send only the fields that changed — everything is optional. There is no fee. Changes are applied after review, and your registration keeps sending under its current approval while an update to an approved registration is reviewed.
Registrations created with create_sub_account=true (the default) live on a sub-account; this resolves to it automatically when there’s exactly one, or honors the X-Sub-Account-Id header.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
E.164 format, e.g. +15551234567
Legal/registered business name.
Public-facing brand name if different from business_name.
Custom title when contact_title is 'other'.
EIN / Tax ID.
e.g. technology, real_estate, retail, healthcare
e.g. ['usa_and_canada']
Street address line 2 (suite, unit, etc.).
State/region code.
Postal/ZIP code.
1-5 specific use cases for your SMS campaign.
2-5 example messages. Each must be 20-1024 chars and include your brand name.
Publicly accessible URL to a screenshot of your opt-in flow (PNG, JPG, WEBP, or GIF, max 2MB)
Response
Set when the update was applied to a registration on a sub-account of the calling account (the default for POST /v1/register).

