Developer integration
Available nowCustom API + WhatsApp via InfiQ
The same REST API that powers InfiQ's own dashboard is yours to build on — messaging, templates, contacts and conversations. Available now, documented, and stable by design.
How the data flows
Custom API
your system
InfiQ
rules + templates
You're all set! We'll keep you posted right here on WhatsApp.
✓✓
delivered · read
Live syncWhy connect
What syncing Custom API unlocks
Four flows teams typically wire up first when Custom API starts talking to WhatsApp.
Full messaging surface
Send approved templates with variables, media and interactive buttons; reply within customer-service windows; and query message status — all over clean REST endpoints.
Templates and media by API
Create and manage message templates programmatically and upload media once for reuse, so releases do not depend on dashboard clicks.
Contacts and conversations
Manage contact lists, opt-in state and custom attributes, and read conversation history — enough to build your own views on top of InfiQ.
Keys in minutes, not meetings
Generate scoped API keys from the dashboard and make your first authenticated call in minutes. Docs with request and response examples live at /developers.
Available on Growth and above
How to get started
This is a core platform capability, available on the Growth plan and above — here is the path from zero to first event.
- 1
Create your API credentials
Sign in to the InfiQ dashboard and generate a scoped API key — it takes about a minute.
- 2
Point events at your endpoint
Register your webhook URL and verify the signature, or make your first authenticated REST call from your backend.
- 3
Send approved templates
Trigger pre-approved WhatsApp templates with live data, and handle inbound replies in the shared team inbox or your own system.
Example flows
- Your backend event → POST /messages → approved template with variables
- Nightly job → contacts API → sync opt-ins and attributes from your database
- Support tool → conversations API → render chat history inside your own UI
Endpoint references, payload examples and sandbox keys are in the developer docs.
This is the product, not a preview
The REST API is a first-class part of the InfiQ platform, included on the Growth plan and above and used in production by our own dashboard. Every native connector we ship is built on this same surface — which is why anything you build here today keeps working as the platform grows.
Where it fits
Teams that pair Custom API with WhatsApp
See how businesses in these industries run the flows above end to end on InfiQ.
Related
Where this integration fits
FAQ
Custom API integration — common questions
Is the API available now?
Yes — the REST API is live today on the Growth plan and above, and it is the same surface the native connectors will be built on. Generate a key in the dashboard and start calling it today.
What can I build with it?
Anything on this integrations page and plenty that is not: transactional notifications from your backend, custom CRM sync, internal tools with embedded chat history, chatbot logic that calls your systems, and scheduled campaign sends.
Do I need developers to use it?
Yes — it is an API, so this path assumes engineering. A typical first integration is a few hours of work with the docs at /developers. If you have no developers, start with Zapier or Make instead, or wait for the native connector for your tool.
Will API integrations break when native connectors launch?
No. Connectors are a convenience layer on the same API, which we version carefully. Anything you build directly keeps working — many teams run both side by side.
Put Custom API on WhatsApp this week.
Start with the API today and switch to the native connector when it lands. Our team will map the flow in a 20-minute call.