REST API + MCP · Official WhatsApp Business API

WhatsApp Business API for Developers

Add WhatsApp to your application without building the entire WhatsApp infrastructure yourself. One clean REST API on the official WhatsApp Business API — messaging, templates, contacts, campaigns, scheduling, webhooks and analytics.

Create free account →Read the API docs
RESTMCPWebhooksTemplatesCampaignsAnalytics

Architecture

Your application talks to Gambot; Gambot talks to WhatsApp. You never touch Meta Graph plumbing, tokens or template submission flows directly.

Your Application
      |
      v
Gambot REST API / MCP        base: https://api.gambot.co.il/api/v1
      |
      v
WhatsApp Business API (Cloud API, official Meta)

Send a message in one request

Authenticate with your organization Gambot token (gmbt_…). Every response uses a consistent { success, message, data } envelope; errors add a machine-readable code.

curl -X POST https://api.gambot.co.il/api/v1/messages/send-text \
  -H "Authorization: Bearer gmbt_your_token" \
  -H "Content-Type: application/json" \
  -d '{ "to": "972501234567", "text": "Hello from my app 👋" }'

# 200 OK
# { "success": true, "data": { "messageId": "wamid...", "to": "972501234567" } }

What the API covers

Real, supported capabilities — no invented endpoints.

✉️

Messaging

send-text, send-template, delivery status, conversations & message history.

📄

Templates

List, read, inspect variables, create (submitted to Meta) and upload media.

👥

Contacts & CRM

Contacts, tags, consent, leads, cases, tasks and notes with custom fields.

📣

Campaigns

Create, schedule, run and read results; opt-out and consent handled automatically.

🔗

Webhooks

Forward inbound WhatsApp events to your endpoint for real-time processing.

📊

Analytics

Message volume, conversations waiting for reply, leads, cases, tasks, campaign performance.

Built for integration

  • Token auth with scopes — pass Authorization: Bearer gmbt_…; keys can be limited to specific scopes.
  • Machine-readable errors — every error returns a stable code (e.g. CONVERSATION_WINDOW_CLOSED, MISSING_TEMPLATE_VARIABLES) so you branch on codes, not prose.
  • Global phone handling — E.164 with per-account country defaults; multi-number orgs pick a sender with from.
  • AI-friendly responses — ISO-8601 timestamps and pruned empty fields keep payloads clean for both code and LLMs.
  • Prefer natural language? The same API is available to AI agents via the WhatsApp MCP server and WhatsApp API for AI agents.

Start building

Create a free account, grab your Gambot token from Settings → General, and make your first API call in minutes.

Create free account →Full API reference →

Frequently asked questions

What is the API base URL and how do I authenticate?

The base URL is https://api.gambot.co.il/api/v1. Authenticate with your organization Gambot token (gmbt_…) via Authorization: Bearer, the X-Api-Key header, or an api_key query parameter. Tokens can be scoped.

Do I need my own Meta / WhatsApp Business API account?

No. Gambot is an official Meta Business Solution Provider and manages the WhatsApp Business (Cloud) API for you — including template submission and number provisioning during onboarding.

How are errors structured?

Responses use { success, message, data }. Errors also include a stable machine-readable code (e.g. CONVERSATION_WINDOW_CLOSED, MISSING_TEMPLATE_VARIABLES, INVALID_PHONE_NUMBER) and, where useful, a data object with state flags to help you recover.

Can I receive inbound messages?

Yes — configure a webhook to forward inbound WhatsApp events to your endpoint, and read history with the conversations endpoints.

Is there an MCP option for AI agents?

Yes. The Gambot MCP server exposes the same functionality as AI-friendly tools for ChatGPT, Claude, Gemini and Cursor. See the WhatsApp MCP page.