POST
Meta Cloud API Compatible
Meta v18.0Drop-in compatibility route for developers migrating from Meta WhatsApp Cloud API. Supports nested `text: { body }` and `template` objects.
Meta Cloud API Compatibility
Point your existing Meta WhatsApp Cloud API SDK base URL to https://api.wahide.com/api/v1 without modifying your request schemas.
HTTP Endpoint
POSThttps://api-wa.hidessh.com/api/v1/v18.0/{deviceId}/messages
Authentication
This endpoint requires Bearer authentication via your secret API Key.
| Header Key | Value | Required |
|---|---|---|
| Authorization | Bearer <your_api_key> | Required |
| Content-Type | application/json | Required |
Request Parameters
The request body must be formatted as JSON with the following parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
messaging_product | string | Required | Always set to 'whatsapp'. example: whatsapp |
recipient_type | string | Optional | Type of recipient. Defaults to 'individual'. default: "individual" |
to | string | Required | Recipient phone number in E.164 international format. example: 628123456789 |
type | string | Required | Message type: 'text', 'image', 'document', or 'template'. example: text |
text | object | Required | Text message payload object containing the body string. |
text.body | string | Required | The actual message content string inside the text object. example: Hello from Meta-compatible route! |
Code Examples
request.sh
curl -X POST "https://api-wa.hidessh.com/api/v1/v18.0/01M1WW3FKR1JS7CW4KGY78Q5ND/messages" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messaging_product": "whatsapp",
"recipient_type": "individual",
"to": "628123456789",
"type": "text",
"text": {
"body": "Hello from Meta-compatible route!"
}
}'Response Formats
Meta formatted 200 OK message response.
application/json • 200 OK
Response Attributes Breakdown
| Attribute | Type | Description |
|---|---|---|
messages[].id | string | Standard Meta WAMID (WhatsApp Message ID). |
On this page