Phound Messaging API v1

Build two-way messaging into your app with a few lines of code.

One API to send and receive SMS and MMS on the Phound business numbers you already own. It handles the parts around the send for you: your numbers, delivery status, 10DLC compliance, replies and safe retries.

Nothing to request, sign in and go REST and JSON Two-way SMS and MMS
POST /messaging/v1/messages
# send a text from one of your Phound numbers
curl https://api.phound.app/messaging/v1/messages \
  -H "Authorization: Bearer $PHOUND_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 5f1c2d0e-order-4471-shipped" \
  -d '{"from": "+13075222720", "to": "+14155550123",
       "text": "Hi Maria, your order has shipped."}'

#=> 202 {"id": "msg_01m3ae8f0pxc3xn1m8pbdt68gp", "object": "message",
         "channel": "sms", "status": {"group": "sent", "final": false}}

# moments later, at your webhook
{"type": "message.delivered", "data": {"id": "msg_01m3ae8f…",
  "status": {"group": "delivered", "final": true}}}

What people build with it

Transactional messaging from the number your customers already know

Send reminders, confirmations and support replies with one API. Every reply lands in the same thread your team already answers in the Phound app, so the conversation never splits between your software and your phone.

01

Appointment reminders

Confirm the booking when it is made, remind the customer the day before, and let them reply to reschedule. A message can be scheduled up to 90 days ahead and cancelled while it waits.

send_atmessage.received

02

Order and delivery updates

Shipped, out for delivery, ready for pickup. An idempotency key on every send means a retried request can never text a customer twice, and a delivery event tells you when it landed.

Idempotency-Keymessage.delivered

03

Support conversations

Replies arrive as events threaded with what you sent, so a customer's text lands in your help desk with its history attached. Reading a conversation back is one request, and search works across all of them.

conversationssearch

How it works

Three steps to your first delivered text

Try each step in the portal's dashboard first, then move it into your code. The dashboard and your code talk to the same API.

Sign in with your Phound account

There is no separate developer account and nothing to request. Sign in to the portal with the Phound account that holds your business numbers, and they are already there, ready to send from. No Phound account yet? Create one and come back.

Create an API key

Make a key with only the scopes it needs: sending, reading, numbers or webhooks. Every request carries it as a bearer token, and a revoked key is refused from the next request on.

Send, and get told what happened

One POST /messages sends. Register a webhook and every delivery status and every reply arrives as a signed event. Not running a webhook endpoint yet? The dashboard has an inbox that shows the events until you are.

Before your first text

Texting from a US number means registering your business first.

US carriers treat a text a business sends from an ordinary ten-digit number as application-to-person messaging, and they require the sender to be registered with The Campaign Registry (TCR) under the 10DLC rules. Traffic from an unregistered number gets filtered or blocked, which is why the API holds every send until your registration is approved.

You submit it from the portal's Registration page and Phound reviews it, usually within a few business days. Numbers, keys, webhooks and reading conversations all work while you wait. If you already registered through Phound Wave or Phound Business, that registration counts here too. How registration works

Have ready

  • Your legal company name, EIN or tax ID, address and website
  • What you will send, and how people agree to receive it, with screenshots of the opt-in
  • A few sample messages that name your business and say how to opt out

Under the hood

What the API takes care of so your code does not have to

You always learn how a message ended

A message.sent event arrives right away, then exactly one final event. Statuses are sorted into six fixed groups, so your code never has to parse carrier codes.

Webhooks you can trust

Each event carries a signature in the Standard Webhooks format, is retried with backoff for about three days if your endpoint is down, and keeps flowing while you rotate the secret.

More than messaging

The same key reaches the Account, Recordings and Calls APIs: your numbers, your call and meeting recordings, and your call history.

Pricing

Messages are billed per SMS segment to your Phound account, and a preview call shows the estimated cost before anything goes out. For volume pricing or higher rate limits, talk to us.

Talk to us

Building something bigger? Tell us about it.

You do not need to ask for access. An API key is self-serve from the portal, and the quickstart gets you to a delivered text in a few minutes. This form is for when you want to talk about volume pricing, higher rate limits, several numbers, or an integration you would like help scoping. A real person reads every one, and most hear back within two business days.

  • Ready to build now? Get an API key with your Phound account, or create a Phound account first.
  • We reply from support@phound.app.
  • Texting from U.S. numbers? Say so below and we will point you at the registration step first, so nothing waits on it later.
What do you want to talk about?
Will you send SMS from U.S. phone numbers?

Good to know now: texting from U.S. numbers needs 10DLC (TCR) registration before the API will send. You submit it from the portal's Registration page, and review usually takes a few business days.

Thanks. Our team will read your note and reply from support@phound.app.

That didn't go through. Check the highlighted fields and try again, or email support@phound.app.

Prefer email? Send the same details to support@phound.app.

Ready to send your first message?

Sign in with your Phound account, create a key, and follow the quickstart to a delivered text that your server is told about. Everything a developer needs lives at developers.phound.app.