Re-run A2P registration for stuck numbers
POST /phone-numbers/a2p/reconcile
Re-attach this organisation’s pending or failed numbers to its A2P messaging service.
The repair step, not the registration step. A worker already does this every six hours; this is how to stop waiting for it after fixing whatever made a number fail. It re-runs against numbers whose status is pending or failed and leaves registered ones alone, so it is safe to call repeatedly.
Tiered as an ordinary write rather than a spend: it reconciles state the
/a2p/register submission already paid for and starts no new registration.
503 means the messaging service is not configured for this environment,
which is a deployment fact rather than anything the caller did wrong.
Authorizations
Parameters
Header Parameters
Responses
200
Successful Response
object
An open envelope for a purchase result, a release, or an A2P job.
Open on purpose. A purchase returns the stored row (whose capability and
provider-metadata keys differ per provider), a workflow start returns a
workflow_id, and the A2P reconcile returns per-number outcomes that grow
as carriers add statuses. Pinning it would silently drop whatever the
provider reported that this contract had not caught up on.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error