Public API
Connect your system to whapi.chat: create API keys and read the developer documentation.
What you can do with the API
whapi.chat has two APIs to connect your system (a CRM, an ERP, n8n…):
| API | What it is for |
|---|---|
| WABA API | Send templates, text, and files through your WhatsApp Business API numbers. |
| CRM API | Read and update leads, contacts, and companies, and read each lead’s history. |
The full technical documentation (guides, a reference for every operation, and examples) is at whapi.chat/desarrolladores. It is currently available in Spanish only.
Create an API key
- Go to Administración → Configuración de la empresa and open the Claves de API tab (admins only).
- Click Crear clave and give it a name that says what it is for (n8n, your ERP, an agency…).
- Copy it right away: it is shown only once. We store an encrypted fingerprint, so it cannot be shown again.
Whoever builds the integration sends it on every request as Authorization: Bearer <key>.
You can have up to 5 active keys. Use one per integration: if you revoke one, the others keep working. The tab shows when and where each key was last used.
If your company had a key before this tab existed, it appears as Clave principal with the Formato anterior label. It keeps working, and you can view and copy it until you regenerate it.
Regenerate or revoke a key
- Regenerar creates a new key with the same name. Before confirming, you see where the current one is used. You choose between:
- Mantener la anterior 7 días (recommended): both work while you update your integrations.
- Invalidar la anterior ahora: for when the key was leaked.
- Revocar turns the key off immediately and cannot be undone.
Every change is logged, and workspace admins are notified by email.
API vs. webhooks
| Webhooks | API | |
|---|---|---|
| Direction | whapi.chat → your system | your system → whapi.chat |
| Where to set it up | Webhooks tab | Claves de API tab |
| Authentication | Signing secret on each delivery | API key |
Changes made through the CRM API do not trigger webhooks back: the API response is the confirmation. More in Outbound webhooks.