# POST /phone/a2p/sync

**Resource:** [Phone](./phone.md)  
**MCP tool:** `sync_a2p_status`  
**Scopes:** `phone:write`  
**Write operation:** yes

Refresh this workspace's US SMS registration against the carrier registry and push it to its next stage if it is ready. Safe to call repeatedly — it does nothing when nothing has changed. Call this when get_a2p_registration looks stuck, or before reporting progress to a client, so you are quoting the live position rather than the last recorded one. It needs the write scope because it does more than read: once a review passes it performs the next step of the sequence for real, which on the final stage means creating the campaign, attaching the number and starting the monthly charge. Returns the same shape as register_a2p: the current status, the stage it reached, and an error if a stage failed. A registration the registry has REJECTED comes back as a normal 200 carrying status "failed" plus the reason, not as an error, because the refresh itself worked and that status is the answer. Always read status rather than assuming a 200 means healthy.

## Parameters

| Name | In | Type | Required | Description |
|------|----|------|----------|-------------|
| `require_approval` | body | boolean | no | Optional. Set true to route this write into the approval queue for human review instead of executing it immediately (returns 202 + an approval_id). Works even when your key/token has permission to execute directly. |

## Request example

```bash
curl -X POST   "https://api.trustpager.com/functions/v1/api/v1/phone/a2p/sync"   -H "Authorization: Bearer YOUR_API_KEY"   -H "Content-Type: application/json"   -d '{"require_approval":"..."}'
```

---
Base URL: `https://api.trustpager.com/functions/v1/api/v1` — Auth: `Authorization: Bearer YOUR_API_KEY`