WhatsApp, SMS & RCS API Documentation

API Base URLs

Production base URLs for each channel. Call them only from your server, over HTTPS. Email and Voice don't have a public API base URL yet; contact us to integrate them.

Authentication

WhatsApp API requests are authenticated with your API key in the apikey request header. Send JSON bodies with Content-Type: application/json. Your API key is issued during onboarding; keep it on your server and never in a browser or mobile app. The SMS and RCS APIs' authentication details are shared with your credentials, because their reference isn't published yet.

apikey: YOUR_API_KEY
Content-Type: application/json

WhatsApp API Reference

Base URL https://whatsappapi.messagify.in/v3. Request bodies use the same JSON structure as Meta's WhatsApp Cloud API, so Meta's message API reference describes every message type and field. Templates must be approved before you can send them; see why WhatsApp templates get rejected.

Endpoints

Sample request: send a template message

Use an approved template for any message sent outside the 24-hour customer service window. Each parameters entry fills the template's next variable, in order.

curl -X POST "https://whatsappapi.messagify.in/v3/PHONE_NUMBER_ID/messages" \
  -H "apikey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "recipient_type": "individual",
    "to": "91XXXXXXXXXX",
    "type": "template",
    "template": {
      "name": "order_update",
      "language": { "code": "en" },
      "components": [
        {
          "type": "body",
          "parameters": [
            { "type": "text", "text": "Asha" },
            { "type": "text", "text": "MSG-1042" }
          ]
        }
      ]
    }
  }'

Sample request: reply with a text message

Free-form text messages can only be sent inside an open 24-hour customer service window.

curl -X POST "https://whatsappapi.messagify.in/v3/PHONE_NUMBER_ID/messages" \
  -H "apikey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to": "91XXXXXXXXXX",
    "type": "text",
    "text": { "body": "Thanks, your appointment is confirmed." }
  }'

Response

A successful send returns the message ID. Store it so you can match the delivery and read events your webhook receives. The response can include other fields as well.

{
  "messages": [
    { "id": "MESSAGE_ID" }
  ]
}

Webhooks

Register one webhook URL per WhatsApp number. Inbound messages, delivery and read-status events are then pushed to it. Callbacks aren't signed, so set a custom header with a shared secret when you register, and reject any callback that doesn't carry it. Respond quickly and process events idempotently, because the same event can arrive more than once. A field-by-field webhook payload reference isn't published yet; log payloads during UAT.

curl -X POST "https://whatsappapi.messagify.in/v3/PHONE_NUMBER_ID/setwebhook" \
  -H "apikey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "webhook_url": "https://example.com/whatsapp/webhook",
    "headers": {
      "x-webhook-token": "YOUR_SHARED_SECRET"
    }
  }'

Check the current configuration with GET /{phone_number_id}/getwebhook.

Errors and Retries

Retry only when it's safe to. A blind retry after an ambiguous failure is the most common cause of duplicate messages.

SMS and RCS APIs

The SMS API (https://smsapi.messagify.in) and RCS API (https://rcsapi.messagify.in) are production hosts, but their endpoint reference, authentication details and sample requests aren't published on this page yet. We share them, with your credentials, during onboarding. Contact our team for access.

Product Documentation

Integration Guides

• Meta for Developers: WhatsApp message API reference
• Meta for Developers: Sending template messages

Integration Workflow

Channel Prerequisites

Each channel has approvals that must be in place before your first production message.

Coming Soon

These are on our roadmap and not yet live — they're listed here so you know what to expect, not as available functionality.

Developer FAQ