If you already integrate with WhatsbizAPI's sendtemplatemessage endpoint, wabapi accepts the same request on a compatibility path. The body — token, phone, template_name, template_language, components — is unchanged, so the switch is two configuration values: the base URL and the token, which becomes your wabapi API key.
POST/api/wpbox/sendtemplatemessage
{
"token": "wab_live_0123456789abcdef0123456789abcdef",
"phone": "917021948630",
"template_name": "ticket_confirmation",
"template_language": "en",
"components": [
{
"type": "body",
"parameters": [
{
"type": "text",
"text": "Prajesh"
},
{
"type": "text",
"text": "Thane"
},
{
"type": "text",
"text": "04:00 PM"
}
]
}
]
}The response and the error codes are the same as the v1 endpoint. Note the path is under /api, not /api/v1.
This path exists so a migration is painless. For new integrations use POST /api/v1/messages/template with the key in the Authorization header: a token in the request body ends up in access logs, proxies and crash reports, and a header does not.