What it is
Wtflo exposes a REST API on your deployed API domain. Tenants use API keys from their workspace; partners integrate external systems (CRM, ERP, custom apps) with the same API.
Base URL: https://<api-domain>/api
Authentication
Tenants generate keys at Account → API keys & developer docs in the chat app.
Authorization: Bearer <api_key>
Content-Type: application/json
Common endpoints
Area Example path Purpose
Messages POST /messages/send Send text or template
Contacts GET /contacts List/search contacts
Templates GET /templates List WhatsApp templates
Webhooks Configure in UI Outbound event notifications
Full interactive docs are built into the tenant app at Account → API keys (Swagger-style reference).
Common integration patterns
Inbound from your site: Form submit → API creates contact → send WhatsApp template
Outbound to your ERP: Wtflo Event webhooks → your endpoint
Sync contacts: Periodic GET /contacts with pagination
Rate limits
Respect Meta WhatsApp throughput limits and your server capacity. Use queues for bulk sends — prefer Broadcast campaigns UI for large blasts.
Security
Store API keys server-side only — never in browser frontend
Rotate keys when staff leave
Use HTTPS for all webhook receivers
Related
Webhook setup
Event webhooks
API keys (tenant feature)
Related articles
API keys & developer docs
Event webhooks