Skip to main content
The Connexease Gateway sits between your application and the Meta WhatsApp Cloud API. You send a single HTTP request with your API key — the Gateway handles authentication with Meta, enforces rate limits, tracks billing, and returns a standard response. This guide walks you through the full flow from key creation to receiving your first delivery confirmation.

Send a Message

Text, media, and template message reference.

Set Up Webhooks

Receive incoming messages and delivery updates.

Authentication

API key management and webhook security.

Error Codes

Messaging API error codes with resolution steps.

Step 1 — Get Your API Key

Sign in to the Connexease Gateway Dashboard, open your application, and go to Developer → API Keys → + Create API Key. Give the key a name, choose an expiry, and copy the value. The key is shown in full only at the moment it is created. Keep it in an environment variable — never commit it to source control.
Never expose your API key in frontend code, mobile apps, or public repositories. All requests must come from your backend server.

Step 2 — Test in Sandbox

Before touching a real WhatsApp number, use is_fake=true to verify your integration end-to-end. The full pipeline runs — auth is checked, rate limits apply, billing balance is validated — but the Meta API call is skipped and a fake message ID is returned. Sandbox mode is a query parameter, not a separate key: use the same API key here as in production.
Response:

Step 3 — Send a Real Message

Remove is_fake and use a real recipient number. Phone numbers must include the country code without +, spaces, or dashes — e.g. 905321234567 or 14155552671.
Response:
Store data.messages[0].id — the wamid — in your database. You’ll use it to match incoming delivery status webhooks in Step 5.

Step 4 — Set Up Your Webhook Endpoint

Go to DashboardApp → Developer → Webhook, enter your HTTPS URL, set a webhook secret, and select the events you want to receive. Your endpoint must return HTTP 200 within 5 seconds. Process events asynchronously.

Step 5 — Track Delivery Status

Once your webhook is live, the Gateway will POST a message_status event every time the delivery state of a message changes. Match it to your original send using the wamid.
isSuccess: true on the send response means the message was accepted, not delivered. delivered only arrives via webhook.

Next Steps

Create Templates

Create and submit templates for Meta approval before you send them.

All Webhook Events

Full payload examples for every event type.

Error Handling

Messaging API error codes with recommended actions.

Billing

How Connexease and Meta fees work.