Send Text Message

Send a free-form text message to a customer. Free-form messages can only be sent inside the 24-hour customer service window — i.e. the customer must have messaged your WABA at least once in the past 24 hours. If the window is closed, use a template message instead.

Endpoint


POST https://apis.splashifypro.com/api/v1/public/message

Headers

Header	Value
`Authorization`	`Basic YOUR_API_KEY`
`Content-Type`	`application/json`

Request body


{
  "fullPhoneNumber": "919876543210",
  "callbackData": "order_12345",
  "type": "Text",
  "data": {
    "message": "This msg is sent via API"
  }
}

Field	Required	Notes
`fullPhoneNumber`	one of `fullPhoneNumber` OR `phoneNumber` + `countryCode`	E.164 without `+` (e.g. `919876543210`)
`phoneNumber`	alternative to `fullPhoneNumber`	Phone without country code, no leading `0`
`countryCode`	required when using `phoneNumber`	E.164 country code with `+` (e.g. `+91`)
`callbackData`	optional	Up to 512 chars — echoed in the delivery webhooks for correlation
`type`	yes	Must be `"Text"`
`data.message`	yes	The text body. Supports WhatsApp formatting: `bold`, `_italic_`, `~strike~`, ```code``` “

Example


curl -X POST https://apis.splashifypro.com/api/v1/public/message \
  -H "Authorization: Basic YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullPhoneNumber": "919876543210",
    "callbackData": "some_callback_data",
    "type": "Text",
    "data": { "message": "This msg is sent via API" }
  }'

Successful response — `201 Created`


{
  "result": true,
  "message": "Message queued for sending via Splashify Pro. Check webhook for delivery status",
  "id": "d58aeff7-a81c-47a7-9b67-f381e13f6c4e"
}

The id is your Splashify message id — use it to correlate with message.sent, message.delivered, message.read, message.failed webhooks.

Error — `400 Bad Request`


{
  "result": false,
  "message": "Please correct the following error - Customer has not messaged within last 24 hours"
}

When the 24-hour window has expired, switch to a template send. The error message names the exact reason — log it on your side for debugging.