Messaging API · v1

Text your customers from your own code, and know when it lands.

The Phound Messaging API sends and receives SMS on the numbers you already have with Phound, and tells your server about every delivery through signed webhooks. Two-way conversations, not bulk blasts.

No new account: sign in with your Phound account and you'll have a key in a minute.

curl https://api.phound.app/messaging/v1/messages \
  -H "Authorization: Bearer $PHOUND_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-4471-shipped" \
  -d '{
    "from": "+13075222720",
    "to":   "+14155550123",
    "text": "Hi Maria, your order has shipped."
  }'
POST https://your-app.example/webhooks · moments later
webhook-signature: v1,K5oZfzN95Z9UVu1Esf…
{
  "type": "message.delivered",
  "data": {
    "id": "msg_01m3ae8f0pxc3xn1m8pbdt68gp",
    "status": {
      "group": "delivered",
      "state": "delivered_to_carrier",
      "final": true
    }
  }
}
How it works

From sign-in to a delivered text in four steps

Everything below can be done from the dashboard first, then copied into your code. It's the same API either way.

Register for 10DLC Required

US carriers only deliver business texts from registered senders. Submit your business's 10DLC registration from the dashboard. Phound reviews it, usually within a few business days, and the API won't send until it's approved, so start here. How registration works

Create an API key

Sign in with your Phound account and create a key with only the permissions it needs. Your numbers are already there.

Send a message

One POST /messages from your server. Conversations are created for you, and an Idempotency-Key makes retries safe.

Get told what happened

Signed webhook events report each message's status and every reply. No webhook server yet? Use the dashboard's built-in inbox.

Delivery you can reason about

Every message ends one way, and you hear about it

You get message.sent right away, then exactly one final event. Switch on six stable status groups instead of a long tail of carrier codes, and never mistake a missing receipt for a failure.

How message status works
Built for production

The details that usually bite, handled

A small, opinionated API for people and small businesses who both send and receive, with the hard parts of messaging designed in from the start.

Conversations, both ways

Replies arrive as message.received, threaded with what you sent, and you can read any conversation back.

Signed webhooks

Every event is signed to the Standard Webhooks spec, retried for days, and its secret rotates without dropping events.

Retries that can't double-text

Send an Idempotency-Key with every message. A timed-out request retried with the same key returns the original.

Errors that say what to do

Every error is a Problem object with a stable code, whether a retry can help, and the next step to take.

Keys with only the access they need

Scope each key to sending, reading, numbers or webhooks. Revoke one and it stops on its very next request.

A test inbox included

Point a webhook at the dashboard's built-in inbox and watch real, signature-checked events arrive before you write a receiver.

Documentation

Start reading

Guides for the common paths, and a complete reference for every API, with this environment's URLs in every example.

Already have Phound? You're set.

Sign in with your Phound account to create an API key, set up webhooks and send your first message.