One request sends the message.

The phone is already on the workspace. Send the key, the number, and the text.

Open the API docs

POST /api/messages

{
  "to": "+254712345678",
  "text": "Your order is ready."
}
202 queued

Three steps. Then it sends.

The key belongs to the workspace, and the workspace already has the phone.

Link the phone

Sign in at dashboard.deltamsg.live and scan the code once.

Copy the key

Create an API key on that workspace. It acts for that phone only.

POST the text

One call queues the message. Delivery stays paced with that phone’s other sends.

Authorization

The key is the only id you send.

Bearer dm_live_your_key on https://api.deltamsg.live/api/messages. A 202 means the message is queued. Read it back from the same path.

Authorization

Bearer dm_live_your_key
Workspace and phone included

POST /api/messages/batch

{
  "text": "Your order is ready.",
  "phones": ["+254712345678", "+254798765432"]
}
202 queued · paced

Bulk

Many numbers, one paced queue.

POST /api/messages/batch with a text and a list of phones. They become a campaign and send in the background with the workspace gap and daily limit. Poll /api/campaigns/{id}/queue for progress.

A laptop on a desk with code on the screen

Replies

Replies come back to you.

Point a webhook at your server. Events are message.sent, message.delivered, message.read, message.failed, and message.inbound. You can also GET /api/messages/inbound. Single campaigns also work on /api/campaigns.

Full reference

Start with the phone you already use.

Get started