Connect Fliok to Anything You Run
Fliok does not ship one-click connectors for individual storefronts or CRMs. It ships a documented REST API and signed webhooks, so you can wire WhatsApp into whatever you already use — including software nobody else has built a connector for.
We would rather be honest about that than list logos we do not support.
What Fliok Connects To Today
The complete list. If it is not here, it is not built — and you can still reach it yourself through the REST API and webhooks.
Meta Cloud API
WhatsAppYour number runs on the official WhatsApp Business Platform. Connect it through embedded signup — no unofficial gateway in the middle.
REST API
Build your ownSend messages and media, read conversations, messages, contacts and templates, and create templates from your own systems.
Outbound Webhooks
Build your ownInbound messages and delivery-status changes POSTed to your server in real time, each signed with HMAC-SHA256.
API Keys
Build your ownIssue scoped Bearer keys per integration, give them an expiry date, watch when they were last used, and revoke instantly.
Click-to-WhatsApp Ads
MetaLeads from your Meta click-to-WhatsApp ads arrive with their ad referral data attached, so the lead is never anonymous.
CSV Import & Export
DataMove contact lists in and out of Fliok as CSV — the simplest bridge to a CRM or spreadsheet that has no API of its own.
Razorpay
BillingPowers your Fliok subscription payment only. It does not collect payments from your customers inside WhatsApp.
Everything the Dashboard Does
The public API is the same surface the product runs on — not a cut-down export.
Send from anywhere
POST a text, template, image, document or interactive message from your backend, your CRM, or a cron job. Media uploads go through the same API.
Read what happened
Cursor-paginated reads for messages, conversations, contacts and templates — including per-message delivery status by id or wamid.
Get pushed, not polled
Register a webhook endpoint and receive signed events — inbound messages, delivery status, failures, template decisions, new contacts, conversation windows and finished broadcasts — as they happen, with retries on failure.
Verify every delivery
Each webhook carries an HMAC-SHA256 signature over the timestamp and raw body, so you can prove the payload came from us.
Send Your First Message in One Request
Issue an API key from your dashboard, then call the endpoint below. Predictable JSON in, predictable JSON out.
POST /api/v1/send
Authorization: Bearer wa_your_api_key
Content-Type: application/json
{
"to": "+919876543210",
"type": "text",
"text": "Hi Rahul! Your order is ready."
}Response 200 OK
{ "id": "…", "status": "queued" }
Note: a text message can only be sent inside an open 24-hour customer service window. Outside it, send an approved template — the same endpoint takes type: "template".
How to Wire It Up
Three steps, and your systems are talking to WhatsApp.
Issue an API Key
Create a Bearer key in the dashboard, pick its role, and optionally give it an expiry date. Copy it once — it is never shown again.
Call the API
Send messages and media, or read conversations, contacts and templates, straight from your own backend.
Receive Webhooks
Register your endpoint and Fliok pushes inbound messages and delivery statuses to you, signed so you can verify them.
Want a Turnkey Connector?
Tell us which tool you need Fliok to talk to natively. We prioritise native connectors by demand — and in the meantime we are happy to help you build it against the API.
Start Building Today
Get started for free and issue your first API key in minutes.