Integration
WispHub notifications from your own number
WispHub can hand every customer message to any HTTP gateway. Point its generic WhatsApp gateway at WaAPI and payment reminders and service notices go out from the WhatsApp account you link by QR code — no template approval, no price per message, nothing to install.
Paste into WispHub's version 2 gateway form
- URL Gateway
https://waapi.app/api/v1/instances/YOUR_INSTANCE_ID/client/action/send-message- Método
POST- Headers
{ "Content-Type": "application/x-www-form-urlencoded", "Authorization": "Bearer YOUR_API_TOKEN" }- Data
{ "chatId": "{destinatario}", "message": "{mensaje}" }- Parámetros extra
- leave empty
Replace YOUR_INSTANCE_ID and YOUR_API_TOKEN with your own. Keep {destinatario} and {mensaje} exactly as written — WispHub replaces them with each customer's number and message. The word Bearer and the space after it belong in the header.
Four steps to the first message
Link the number that should send
Create an instance in WaAPI and scan its QR code with the phone whose WhatsApp account your customers should hear from. The number at the end of the instance page's address (…/account/instances/123) is the YOUR_INSTANCE_ID in the gateway URL.
Create an API token
Under API Tokens in your account. The default permissions are enough. Copy the token when it is shown — it is displayed only once.
Fill in WispHub's gateway form
Use the values above in the gateway form WispHub labels version 2. WispHub keeps customer mobiles in national format without the country code; check that each customer's number is stored that way and has Enviar avisos SMS switched on.
Send a test from the client list
WispHub lets you send a custom message to one client once the gateway is saved. Send it to a client whose mobile is your own number, and check your phone. On a trial, that number must be your test number — see below.
Testing on a free trial
A trial instance sends to one number only: the Trial phone number on the instance's page. Set it to your own mobile, then give one WispHub client that same number and send the test to that client. It does not matter whether WispHub writes the number with or without a leading +.
A trial allows 15 actions every 5 minutes. Once you subscribe, the same settings send to every customer — nothing in WispHub changes.
Check the token and instance from a terminal first
curl -X POST https://waapi.app/api/v1/instances/YOUR_INSTANCE_ID/client/action/send-message \
-H "Authorization: Bearer YOUR_API_TOKEN" \
--data-urlencode "chatId=+573001234567" \
--data-urlencode "message=Prueba desde WispHub"The same request WispHub sends, with your test number in place of {destinatario}. If this arrives on your phone, any remaining problem is in the WispHub form.
Still on the older form?
WispHub's first generic gateway form has fixed fields instead of free headers. It works too — fill it in like this.
| Field in WispHub | Value |
|---|---|
| URL Gateway | The same URL as above |
| Parámetros (Payload) | chatId={destinatario}&message={mensaje} |
| Método | POST |
| Token de autorización | Bearer YOUR_API_TOKEN — with the word Bearer and a space |
| Content/type | application/x-www-form-urlencoded |
| Código de País | Your country's code |
| Límite de caracteres | Raise it from 160 to your longest message. WaAPI does not shorten messages; WispHub's own examples use 1000. |
What an error means
When a message does not arrive, the status code of WaAPI's answer names the field to fix. The curl check above prints the full answer.
| Answer | What to fix |
|---|---|
| 401 Unauthenticated | The token is wrong, deleted, or missing the word Bearer in front. |
| 403 … only able to send actions to … | A trial, and the client's number is not your trial phone number. |
| 404 Resource not found | The instance ID in the URL Gateway is wrong. |
| 422 … invalid phone number | The number starts with a 0 or is too short — the country code is missing. Check Código de País and the client's stored mobile. |
| 200, but data.status is error | The request arrived and the message was refused — data.message and data.explanation say why. |
WispHub questions
What the connection does and where its limits are.
-
No. WispHub's generic gateway form sends a plain HTTP request per message, and WaAPI's send endpoint accepts it as it is. There is nothing to install on either side.
-
The WhatsApp account you linked to the instance by QR code — your business number or any other. Replies arrive on that phone as usual.
-
No. Billing is a flat rate per connected account, so a month with many payment reminders costs the same as a quiet one.
-
No. WaAPI accepts the number with or without a leading +, and with or without the @c.us suffix. It must include the country code, which is what Código de País adds in WispHub.
-
WhatsApp restricts accounts that send the same text to many people who never wrote to them. Messaging your own customers, who know your number, is the safe case. The article on preventing bans in our blog covers pacing.
-
No. WaAPI is an independent service, and WispHub is a product of its own company. This guide follows WispHub's public documentation of its gateway form as of October 2026; if a field is named differently in your WispHub, the values stay the same.
Connect an account and start sending
One flat rate per connected account. Unlimited messages, no approval process, no per-message invoice.