API and webhooks

WhatsApp API Kuwait: connect your system to your customer chats

WhatsApp API Kuwait for developers and system owners: receive customer messages on a signed webhook, answer them from your own system or an n8n bot with one REST call, and hand the conversation to an agent when it needs one. All on the numbers you have connected to E3lanition.

curl -X POST https://e3lanition.com/api/v1/messages \
  -H "Authorization: Bearer e3l_live_…" \
  -H "Content-Type: application/json" \
  -d '{"conversationId": "cm…",
       "text": "Order 1042 is on the way"}'

200 OK
{"id": "cm…", "waMessageId": "wamid.…",
 "status": "sent", "conversationId": "cm…"}

How it works

1

Create an API key

The account owner creates it in settings. It starts with e3l_live_ and is shown once; we keep its SHA-256 fingerprint, not the key. Send it on every request as Authorization: Bearer.

2

Receive events on a webhook

Add an https URL for your system and pick its events: message.received, message.status and message.media.ready, then verify each request's signature with that URL's secret.

3

Reply from your system

Send the answer to POST /api/v1/messages with the conversationId from the event, or hand the conversation to an agent through handoff with a reason.

What you get

Scoped API keys

Each key carries the messages:send and conversations:write scopes, its prefix and last use show in the dashboard, and it can be revoked at once. Up to 5 active keys at a time, so you can rotate without downtime.

Four REST endpoints

Send a text message of up to 4096 characters, set a conversation to OPEN, PENDING or RESOLVED, hand it to an agent and assign them by email, and add an internal note the customer never sees.

HMAC-signed webhooks

Every request carries an X-E3lanition-Signature header: sha256= followed by the HMAC-SHA256 of the raw body under the URL's secret. The body carries the event time, and you can generate a new secret at any time.

Automatic retries

If your system does not answer with success within 10 seconds, we retry up to 5 times with delays that double from 5 seconds, and keep a record of every delivery with its status, response code and attempts for 30 days.

SSRF protection

Only https URLs are accepted; localhost, private and local addresses and the 169.254 cloud metadata address are refused; every DNS record is checked and we connect to the address we checked; 3xx redirects are never followed.

Media through message.media.ready

When a customer sends a photo or a file, this event reaches you once the file is stored, with a signed link valid for one hour, its type, name and size.

Examples from Kuwait

Delivery companies

A delivery company in Ardiya receives "where is my order?" through message.received, looks the shipment up by the customer's number and answers with its status through POST /api/v1/messages within seconds.

Digital marketing agencies

A marketing agency in Qibla runs an n8n bot on a client's number in external-bot mode; it answers repeat questions and hands price-quote requests to the sales agent through handoff, with the reason.

Insurance companies

An insurance company in Salhiya receives accident photos through message.media.ready, files them in its claims system within the hour, then adds the claim number as an internal note on the conversation.

Frequently asked questions

No. It sends text messages to a customer who wrote to you in the last 24 hours on WhatsApp, or any time on Telegram once the customer has started the chat. Outside the window it answers with outside_service_window. Templates and campaigns are sent from the dashboard.

Connect your system to WhatsApp conversations

API keys and signed webhooks come with the Pro plan. Compare the plans and pick the one that fits your team.

See plans