US App to Person Messaging Service Use Case Resource
This resource is related to United States A2P 10DLC registration. For more information on A2P 10DLC registration, please see our support article What is A2P 10DLC?
The US App to Person (A2P) Messaging Service Use Case Resource allows you to fetch possible A2P use cases for a Messaging Service. The use cases that are returned as a response are determined by the use cases that your US A2P Brand is qualified for. There are several Standard and Special use case types.
With this REST API you can:
US App to Person Messaging Service Use Case Resource Properties
| Resource Properties in REST API format | |
|---|---|
us_app_to_person_usecases
|
Human readable name, code, description and post_approval_required (indicates whether or not post approval is required for this Use Case) of A2P Campaign Use Cases. |
Fetch Possible US A2P Campaign Use Cases for a Messaging Service
https://messaging.twilio.com/v1/Services/{MessagingServiceSid}/Compliance/Usa2p/Usecases
Parameters
| Parameters in REST API format | |
|---|---|
messaging_service_sid
Path
|
The SID of the Messaging Service to fetch the resource from. |
brand_registration_sid
Optional
|
The unique string to identify the A2P brand. |
Example 1
Below is a list of Standard and Special campaign use case types for A2P 10DLC. Special use cases my qualify for increased messaging throughput, and may also qualify for reduced carrier fees.
For more information on campaign use cases, please see List of Campaign Use Case Types for A2P 10DLC Registration (support article).
|
Standard Use Case Types |
Special Use Case Types |
|
|
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
