curl --request POST \
--url https://api.watx.in/v1/messages \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"to": "+919876543210",
"type": "text",
"text": "Your order has been packed."
}
'{
"data": {
"message_id": "9d1f4b2a-6c3e-4a51-bf2d-0a7c9e114b3f",
"whatsapp_message_id": "wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgS",
"conversation_id": "3c5b1e77-90aa-4c0e-8f71-1d2a3b4c5d6e",
"contact_id": "7e2d9c01-55b4-4a3d-9c8e-0f1a2b3c4d5e",
"contact_created": false
}
}Messages
Send a message
Sends a WhatsApp message to a phone number. You pass a number, not an internal id: the endpoint finds or creates the contact and the WhatsApp conversation, then sends.
A free-form message (text or media) only reaches a customer inside the
24-hour customer service window. Outside it, send type: "template"
with an approved template.
Templates are looked up by name and language among the
workspace’s synced templates. Send body values as a plain array, or as
an object when the template also needs a header, button values or
carousel cards. Every value the template needs is checked before
anything is sent: a missing or blank one is refused with 502
meta_error and a message naming it. On the Templates screen, the
code button on a template shows the exact request for that template.
One-time codes. For an approved template in the Authentication
category, send the code as the only value: params: ["482913"], up
to 15 characters. WhatsApp puts it in the message and on the
template’s copy-code or autofill button. Your system generates the
code and checks it when the user types it back; Watx only delivers
it.
Sending happens on WhatsApp only.
Requires the messages:send scope.
POST
/
messages
curl --request POST \
--url https://api.watx.in/v1/messages \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"to": "+919876543210",
"type": "text",
"text": "Your order has been packed."
}
'{
"data": {
"message_id": "9d1f4b2a-6c3e-4a51-bf2d-0a7c9e114b3f",
"whatsapp_message_id": "wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgS",
"conversation_id": "3c5b1e77-90aa-4c0e-8f71-1d2a3b4c5d6e",
"contact_id": "7e2d9c01-55b4-4a3d-9c8e-0f1a2b3c4d5e",
"contact_created": false
}
}Authorizations
Your workspace API key, created in Settings → Developer → API keys, sent as
Authorization: Bearer <key>. New keys start with watx_live_; keys
issued before the rename start with converse360_live_ and still work.
Body
application/json
The recipient's phone number in E.164 form, for example
+919876543210. A number without a country code is read using the
workspace's default country.
Example:
"+919876543210"
What kind of message to send.
Available options:
text, template, image, video, document, audio The message body for type: "text", or the caption for an image,
video or document. A caption is capped at 1024 characters.
Public URL of the file. Required for image, video, document
and audio.
The file name shown in the chat for a document.
A name for the contact. Used when this number is new, and updates the name if it differs from the one on file.
Required for type: "template".
Show child attributes
Show child attributes
Quote an earlier message. It must belong to the same conversation.
Response
The message was accepted by WhatsApp and stored.
Show child attributes
Show child attributes