REST · webhooks · documented

Your system talks to your customers directly

Ready integrations cover most shops. Anyone with their own system — an ERP, a booking platform, an app they built — needs to send the message from inside it and receive the reply there. That is what the API is for.

  • REST with a key
  • Webhooks for events
  • Across every channel
Your system
online
POST /messages · template: order_confirm · to: 2010xxxxxxx From your system · 200 OK
Yes, confirm the order
webhook → message.received · your system updates the order In real time
RESTSend and read on one key
A webhook the moment a message arrives or its status changes
3Three channels behind one interface — WhatsApp, Messenger, Instagram

The API absorbs the differences between channels: you send the same way to WhatsApp, Messenger and Instagram.

The problem

What it saves over integrating with Meta directly

You can integrate with Meta directly. Then you own: template approval and its status, conversation categorisation and accounting, retries on failure, webhook signatures, the differences between channels, and storing conversations tied to a customer. Most of that is not your product — it is the toll for reaching it.

How it works

From key to first message

Create a key

From the dashboard, scoped to what your system needs and no more.

Send the first message

One POST with an approved template, the recipient and its variables.

Receive the events

Register a webhook URL that receives message arrival, status change and the customer's reply — signed so you can verify it.

Wire it to your system's state

Update the order, close the ticket, or start a follow-up sequence — from inside your own system.

What you get

What you can do

Send a template or free text

A template to open a conversation, free text inside the 24-hour window. The distinction is Meta's, not ours.

Signed webhooks

An event per message and status, signed so you can verify it — never trusting a request whose origin you cannot check.

One interface, three channels

WhatsApp, Messenger and Instagram in the same shape, so you do not write three integrations.

Retries and a log

Transient failures are retried automatically, and every call has a log showing what you sent and what Meta answered.

Compared

Through the platform versus integrating with Meta directly

Integrating with Meta directly ArabyBot
Template approval and its status You own it Handled
Three channels Three integrations One interface
Retries and a log You build it Built in
Meta's fees On your account On your account, no markup
FAQ

Questions people actually ask

Do I need the API if I use WooCommerce or Salla?

No. The store integrations are ready and need no code. The API is for anyone whose system has no ready integration.

Can I use my existing number?

Yes, provided it is not in use on the WhatsApp app — or you move it through coexistence mode. That is Meta's condition, not ours.

Who pays Meta's fees?

They are billed to your own account with no markup from us. Details in the pricing guide.

Wire your system in a day

REST and signed webhooks · three channels, one interface · Meta fees at cost

Start free