Messaging
Send and receive SMS across every US carrier
One REST endpoint, GSM-7 and UCS-2 handled for you, delivery receipts on every message, and inbound webhooks that arrive in under a second. Built for A2P traffic that has to survive carrier filtering.

01
Segment accounting you can audit
We return the exact segment count and encoding for every message before you are billed for it, so your unit economics never come as a surprise at the end of the month.
02
Automatic opt-out handling
STOP, UNSUBSCRIBE, CANCEL, END, and QUIT are intercepted at the platform level, suppressed across your account, and surfaced to you through a webhook. The suppression list cannot be disabled.
03
Delivery receipts that mean something
We pass through the carrier-level status rather than collapsing everything into 'sent'. When a message is blocked you get the reason code, not a shrug.
04
Inbound in real time
Replies are delivered to your webhook with signature verification, automatic retries with exponential backoff, and a replay endpoint for anything your endpoint missed.
Send your first message
Authentication is a key pair over HTTPS basic auth. There is no SDK requirement โ every endpoint is plain REST.
curl https://api.anthonyoliva.com/v1/messages \
-u "$AO_KEY_ID:$AO_KEY_SECRET" \
-H "Content-Type: application/json" \
-d '{
"from": "+13155550142",
"to": "+13155550188",
"body": "Anthony Oliva: your verification code is 481920.",
"campaign_id": "C7X4M2P"
}'Specifications
- Number types
- 10DLC local, toll-free
- Encoding
- GSM-7 and UCS-2, detected automatically
- Max length
- Unlimited, automatically concatenated
- Throughput
- Assigned by carrier, based on brand trust score and use case
- Delivery receipts
- Included, no additional charge
- Inbound messages
- Free
- Webhook retries
- 5 attempts over 30 minutes
Common use cases
- One-time passcodes and account verification
- Appointment and delivery notifications
- Order and shipping status
- Two-way customer support conversations
- Marketing to recipients who gave written consent
Consent still comes first
Every use case above assumes the recipient gave you prior express consent for that specific program. Our Messaging Policy sets out exactly what your call-to-action must disclose and how long you have to keep the proof.

Talk to someone who has read the carrier rules
Tell us what you are sending, to whom, and how they consented. We will tell you honestly whether it will get approved, and what to change if it will not.