Sending Messages

Every send endpoint lives under https://api.callmissed.com/api/v1/whatsapp, takes a JSON body, needs the whatsapp:send scope (media upload needs whatsapp:write, media reads need whatsapp:read), and identifies the sending number with phone_id or phone_number_id. See WhatsApp API for the selector and the shared error shape.

Free-form sends need an open window. Text, media, interactive and location sends only work inside the 24-hour customer service window that opens when the customer last messaged you. Outside it, send an approved template. A closed-window send returns 422.

The common response

Every send endpoint returns the same object:

{
  "wamid": "wamid.HBgMOTE5MDAwMDAwMDAwFQIAERgSMkE5N0Y4RDcxMkYzQTJEMQA=",
  "wamids": ["wamid.HBgMOTE5MDAwMDAwMDAwFQIAERgSMkE5N0Y4RDcxMkYzQTJEMQA="],
  "contacts": [
    { "input": "+919000000000", "wa_id": "919000000000" }
  ]
}

Track delivery against wamids, not wamid: WhatsApp reports status per message, so a split reply produces several status events.

Sends are persisted into the matching conversation thread, so anything you send over the API shows up in the dashboard inbox alongside the agent's own replies. Reactions are the exception, since a reaction is a property of the message it targets rather than a bubble of its own.

Before WhatsApp is called

Two gates run on every send, before any request reaches Meta.

Tenant scope. The sending number is resolved against your workspace. A number you do not own returns 404, identically to one that does not exist.

Credit check. The charge for a WhatsApp message lands after Meta delivers it, so a send you cannot pay for cannot be undone. Sends are therefore priced up front, against the same rate card the delivery charge uses, and refused with 402 when the balance will not cover them. Nothing is sent and nothing is charged.

{
  "detail": "Not enough credits to send this message, so nothing was sent and nothing was charged. It needs at least 7.51 credits and you have 2.00 spendable (balance 12.00, 10.00 held for running campaigns) -- short by 5.51. Top up your balance and try again."
}

Template sends are priced from the recipient's region and the template's category, which differ by more than tenfold across markets, so the quoted figure is specific to the message you tried to send. Reactions are not credit-gated, because they are not billed.

Send a text message

POST /api/v1/whatsapp/messages · scope whatsapp:send

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "text": "Your order AC-10294 shipped this morning. Track it at https://acme.example.com/t/AC-10294",
    "preview_url": true
  }'

Failures

Send a template message

POST /api/v1/whatsapp/messages/template · scope whatsapp:send

The only way to message someone outside the 24-hour window. The template must already be APPROVED.

components follows WhatsApp's own shape, so any combination WhatsApp supports works: header media, body variables, URL button suffixes. Authentication templates (one-time codes) are sent the same way, with the code as a body or button parameter.

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/template \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "template_name": "order_shipped",
    "language_code": "en_US",
    "components": [
      {
        "type": "body",
        "parameters": [
          { "type": "text", "text": "Priya" },
          { "type": "text", "text": "AC-10294" }
        ]
      },
      {
        "type": "button",
        "sub_type": "url",
        "index": "0",
        "parameters": [{ "type": "text", "text": "AC-10294" }]
      }
    ]
  }'

Returns the common send response. 422 if the template name or locale does not resolve to an approved template on the WABA, and 402 if the priced send exceeds your spendable balance.

Send media

POST /api/v1/whatsapp/messages/media · scope whatsapp:send

Reference the file by an uploaded media_id (recommended, reusable for 30 days) or by a public link that WhatsApp fetches and caches briefly.

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/media \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "kind": "document",
    "media_id": "1079235482913746",
    "filename": "invoice-AC-10294.pdf",
    "caption": "Your invoice"
  }'

Failures

Send an interactive message

POST /api/v1/whatsapp/messages/interactive · scope whatsapp:send

Reply buttons, a list menu, a call-to-action URL button, or a Flow. interactive_type selects the variant.

Common fields

Variant fields

Flow fields (interactive_type: "flow" only)

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/interactive \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "interactive_type": "button",
    "body_text": "Your order is out for delivery. Is someone home to receive it?",
    "footer_text": "Acme Coffee",
    "buttons": [
      { "id": "home_yes", "title": "Yes, deliver" },
      { "id": "home_no", "title": "Reschedule" }
    ]
  }'

Returns the common send response. The customer's tap arrives back on your webhook as an inbound message with type: "interactive" or type: "button". A completed flow arrives as an interactive reply carrying your flow_token alongside the screen data the customer submitted, so use flow_token to tie the submission back to the order, booking or ticket you sent it for.

Failures

Send an order details message

POST /api/v1/whatsapp/messages/order_details · scope whatsapp:send

An itemised bill the customer can pay from the chat with UPI. Needs a payment configuration on the WABA first, see WhatsApp Payments. India and UPI only: any other payment_type returns 501.

Money is integer minor units. Every amount is { "value": …, "offset": 100 }, where value is paise and offset must be 100, so ₹499.00 is { "value": 49900, "offset": 100 }. Floats are not accepted, because binary floating point cannot represent decimal currency exactly and this is a bill.

The order object

total_amount.value must equal subtotal + tax + shipping - discount. Using a custom item image limits the order to 10 items.

The beneficiaries shape — required for shipped physical goods, and India-only:

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/order_details \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "reference_id": "AC-10294",
    "goods_type": "physical-goods",
    "payment_configuration": "acme-upi",
    "body_text": "Here is your order. Pay with any UPI app to confirm it.",
    "footer_text": "Acme Coffee",
    "total_amount": { "value": 61800, "offset": 100 },
    "order": {
      "type": "quick_pay",
      "status": "pending",
      "items": [
        {
          "name": "Ratnagiri Dark Roast 500g",
          "amount": { "value": 55000, "offset": 100 },
          "quantity": 1
        }
      ],
      "subtotal": { "value": 55000, "offset": 100 },
      "tax": { "value": 6800, "offset": 100, "description": "GST 12%" },
      "expiration": { "timestamp": 1776000000, "description": "Pay within 30 minutes" }
    },
    "preferred_payment_methods": [{ "method": "gpay" }]
  }'

Returns the common send response.

Always follow up with an order status update. The customer's order screen keeps showing "Order pending" until you send one, so an order that was paid still looks unpaid.

Failures

Send an order status update

POST /api/v1/whatsapp/messages/order_status · scope whatsapp:send

The update that settles a bill. It moves the customer's order screen off "Order pending" and updates the buttons on the original order details message. Send one on every transaction update.

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/order_status \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "reference_id": "AC-10294",
    "status": "shipped",
    "body_text": "Your order is on its way and should arrive by Thursday.",
    "description": "Picked up by the courier this morning",
    "footer_text": "Acme Coffee"
  }'

Returns the common send response. 400 for an unknown status or a reference_id outside the allowed charset, and 422 when the window is closed or WhatsApp rejected the update.

Send a location

POST /api/v1/whatsapp/messages/location · scope whatsapp:send

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/location \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "latitude": 19.076,
    "longitude": 72.8777,
    "name": "Acme Coffee Bandra",
    "address": "Linking Road, Bandra West, Mumbai 400050"
  }'

Send a reaction

POST /api/v1/whatsapp/messages/reaction · scope whatsapp:send

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/reaction \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "message_id": "wamid.HBgMOTE5MDAwMDAwMDAwFQIAEhggQjc0RTI5RDNBMjJDNjE4RgA=",
    "emoji": "👍"
  }'

Send contact cards

POST /api/v1/whatsapp/messages/contacts · scope whatsapp:send

curl -X POST https://api.callmissed.com/api/v1/whatsapp/messages/contacts \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number_id": "1234567890",
    "to": "+919000000000",
    "contacts": [
      {
        "name": { "formatted_name": "Acme Support", "first_name": "Acme", "last_name": "Support" },
        "phones": [{ "phone": "+918080247309", "type": "WORK", "wa_id": "918080247309" }],
        "emails": [{ "email": "support@acme.example.com", "type": "WORK" }]
      }
    ],
    "biz_opaque_callback_data": "escalation-4471"
  }'

Mark a message as read

POST /api/v1/whatsapp/messages/{message_id}/read · scope whatsapp:send

{message_id} is the wamid of the inbound message. Shows blue ticks, and optionally a typing bubble while you prepare a reply.

curl -X POST "https://api.callmissed.com/api/v1/whatsapp/messages/wamid.HBgMOTE5MDAwMDAwMDAwFQIAEhggQjc0RTI5RDNBMjJDNjE4RgA=/read" \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "phone_number_id": "1234567890", "typing_indicator": true }'

Response (200 OK)

{ "success": true }

The agent does this automatically for messages it answers.

Media

Upload media

POST /api/v1/whatsapp/media · scope whatsapp:write

Multipart upload. The MIME type is read from the file part's Content-Type, so set it explicitly, and it is validated against WhatsApp's allowlist before the request reaches Meta. The returned media_id is reusable for 30 days and is scoped to the number you uploaded it against. Maximum upload size is 100 MB, and this path is rate limited more tightly than the rest of the API.

curl -X POST https://api.callmissed.com/api/v1/whatsapp/media \
  -H "Authorization: Bearer cm_your_api_key" \
  -F 'phone_number_id=1234567890' \
  -F 'file=@invoice-AC-10294.pdf;type=application/pdf'

Response (200 OK)

{
  "media_id": "1079235482913746",
  "mime_type": "application/pdf",
  "size_bytes": 84213
}

Pass media_id to send media.

Failures

Resolve inbound media to a URL

GET /api/v1/whatsapp/media/{media_id} · scope whatsapp:read

Turns a media id into a temporary download URL. Mostly used for inbound media, where the webhook gives you a media id and you want the file. The URL is valid for about five minutes and requires WhatsApp's own auth, so fetch it immediately or use the content proxy instead.

curl "https://api.callmissed.com/api/v1/whatsapp/media/1079235482913746?phone_number_id=1234567890" \
  -H "Authorization: Bearer cm_your_api_key"

Response (200 OK)

{
  "url": "https://lookaside.fbsbx.com/whatsapp_business/attachments/?mid=1079235482913746",
  "mime_type": "image/jpeg",
  "sha256": "b1946ac92492d2347c6235b4d2611184a3e0f5b1c2d3e4f5a6b7c8d9e0f1a2b3",
  "file_size": 84213
}

Stream inbound media bytes

GET /api/v1/whatsapp/media/{media_id}/content · scope whatsapp:read

Streams the raw file back through CallMissed with the upstream content type, so your browser or mobile client can render inbound images without handling short-lived URLs or WhatsApp credentials. Responses carry Cache-Control: private, max-age=300.

curl "https://api.callmissed.com/api/v1/whatsapp/media/1079235482913746/content?phone_number_id=1234567890" \
  -H "Authorization: Bearer cm_your_api_key" \
  --output inbound-image.jpg

Returns the file bytes on 200, or 404 when the media id no longer resolves.