Link a number by QR code. Share one inbox, run campaigns, and send messages and login codes over REST.
curl https://app.getoxtro.com/v1/messages \
-H "Authorization: Bearer $OXTRO_API_KEY" \
-H "Idempotency-Key: order-4821-confirmation" \
-H "Content-Type: application/json" \
-d '{
"connection_id": "conn_ucwapo2sb4j4dvdl",
"to": "+213555123456",
"text": "Your order ORD-4821 has been confirmed."
}'202 Accepted
{
"id": "msg_v72ac6h57g1iabdt",
"status": "queued",
"queued_at": "2026-10-10T09:41:07.000Z"
}curl https://app.getoxtro.com/v1/otp/send \
-H "Authorization: Bearer $OXTRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"connection_id": "conn_ucwapo2sb4j4dvdl",
"to": "+213555123456",
"code_length": 6,
"expires_in_minutes": 5
}'200 OK
{
"request_id": "otp_f5c2tqgh0s9wfu72",
"expires_in": 300,
"status": "sent"
}curl https://app.getoxtro.com/v1/otp/verify \
-H "Authorization: Bearer $OXTRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"request_id": "otp_f5c2tqgh0s9wfu72",
"code": "492821"
}'200 OK
{
"verified": true,
"request_id": "otp_f5c2tqgh0s9wfu72",
"phone_number": "+213555123456",
"verified_at": "2026-10-10T09:42:31.000Z"
}Your order ORD-4821 has been confirmed.
Status:Queued
Agents answer customers, marketers send campaigns, and nobody passes a phone around the office.
Every conversation from every connected number lands in one inbox. Agents reply side by side and see when a message was delivered and read.
Hi, is order ORD-4821 on its way?09:38
It left the warehouse this morning. You will get it tomorrow.09:41
Scan once with the phone that owns the number. Add more numbers to the same workspace whenever you need them.
Write a message once, then fill it per contact from the app or the API.
Your order {{order_number}} is on its way. It arrives on {{delivery_day}}.
Your order ORD-4821 is on its way. It arrives on Tuesday.
Import contacts from a CSV file, tag them, pick a template and send. Messages go out through a queue at a controlled rate, and each recipient is tracked from queued to read.
X-Webhook-Event: message.received
X-Webhook-Signature: t=1791625512,v1=9c1e47…
X-Webhook-Delivery: del_q3m8x1v7k2c9n4bt
{
"event": "message.received",
"timestamp": "2026-10-10T09:45:12.000Z",
"workspace_id": "ws_w8g26w7n8pg1dfih",
"data": {
"message_id": "msg_veahwyvz5bxphd3w",
"conversation_id": "conv_yd30nuc8mxqpk7gp",
"from": "213555123456",
"sender_name": "Customer",
"type": "TEXT",
"content": "Is my order on its way?",
"received_at": "2026-10-10T09:45:11.000Z"
}
}Recent deliveries
WhatsApp messaging API
Send text, media or a saved template from any connected number. Requests are queued, and you can look up the status of any message by its ID.
Subscribe an endpoint and Oxtro tells your backend what happened, including replies from your customers.
message.
connection.
otp.
Two endpoints cover sign-up, login and checkout verification. Oxtro handles generation, expiry and rate limits.
Call /v1/otp/send with a phone number. Oxtro generates the code, so your servers never handle it.
POST /v1/otp/send
{ "to": "+213555123456" }The code arrives in a chat from your own number, using wording you set in an OTP template.
492821 is your verification code. It expires in 5 minutes.
Send what the user typed to /v1/otp/verify and get back a plain yes or no.
The API response appears here.
Invite the whole company. Each person sees the part of Oxtro their job needs.
| Area | Owner | Admin | Developer | Agent |
|---|---|---|---|---|
| Shared inbox, conversations and contacts | Yes | Yes | No | Yes |
| Numbers, API keys, webhooks and logs | Yes | Yes | Yes | No |
| Members, invites and workspace settings | Yes | Yes | No | No |
| Ownership of the workspace | Yes | No | No | No |
Something else? contact@getoxtro.com
No. You link a WhatsApp number you already own by scanning a QR code, the same way you link WhatsApp Web. There is no application or template review step.
No. Oxtro connects to your own WhatsApp account through a linked-device session and does not use the WhatsApp Cloud API. WhatsApp terms still apply to your number, so message people who expect to hear from you.
Yes. A workspace can hold several connected numbers, and every API request names the connection it sends from. How many numbers you can connect depends on your plan.
Text, images, video, audio, documents, locations and contact cards. You can write the message inline or render a saved template with variables.
Register a webhook endpoint. Oxtro posts signed events for received messages, sent, delivered, read and failed statuses, connection changes and OTP activity, and retries deliveries that fail.
Codes are stored hashed, expire after a period you set, and stop working after a maximum number of attempts. Resend cooldowns and per-phone limits slow down abuse.
No. Oxtro delivers over WhatsApp only.
Plans differ by connected numbers, team members, monthly messages, campaign recipients and OTP requests. Current plans are listed on the billing page of your workspace.
Create a workspace, scan the QR code and send a message.
Create account