---
title: "Verify Twilio Us A2P Compliance"
method: POST
path: "/api/v1/channels/twilio/{channel_id}/numbers/verify-a2p-compliance"
tags: ["channels.twilio.numbers"]
---

# Verify Twilio Us A2P Compliance

`POST /api/v1/channels/twilio/{channel_id}/numbers/verify-a2p-compliance`

## Request

- Base URL: `https://api.syllable.cloud`
- URL: `https://api.syllable.cloud/api/v1/channels/twilio/{channel_id}/numbers/verify-a2p-compliance`
- Auth: API key in header `Syllable-API-Key`

Return whether Twilio shows this number on a US A2P messaging path with an approved brand.

## Path parameters

- `channel_id` integer, required

## Request body

- A2pMessagingPathCheckRequest: Body to check US A2P / Messaging Service setup for one number on the Twilio channel.
  - `phone` string, required: E.164 phone number exactly as Twilio stores it for this incoming number.

## Response `200`

Successful Response

- A2pMessagingPathCheckResponse: Twilio-side A2P setup state for the number. Reflects Twilio configuration (Messaging Service + Brand + Campaign records); it is not carrier per-number REGISTERED state or legal/content compliance.
  - `a2p_approved` boolean, required: True when the number is on a Messaging Service with a US A2P registration whose brand is approved and campaign is verified on the same registration.

## Other responses

- `422`: Validation Error

## Changes

> 279 revisions in range; 1 not diffed.

- **2026-04-24** `875019f2f5bf`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/asksyllable/apis/syllablesdk/changes/api/v1/channels/twilio/:channel_id/numbers/verify-a2p-compliance/post.md)

---

[API](https://skmtc.dev/asksyllable/apis/syllablesdk.md) - [All operations](https://skmtc.dev/asksyllable/apis/syllablesdk/llms.txt) - [OpenAPI document](https://skmtc.dev/asksyllable/apis/syllablesdk/revisions/879e5c81a183?raw)