Developer platform

WhatsApp, exposed as a clean API.

Embedded Signup, encrypted Meta tokens and message state tracking are infrastructure problems. Your product should call a documented REST API and receive signed events.

Start building API reference

Versioned /api/v1Scoped keysSigned webhooksMCP connectors

Integration model

You never touch Meta credentials.

A customer authorizes your application. Your backend calls ClickMaker with a scoped key. ClickMaker resolves the encrypted Meta token server-side and dispatches through the customer's own WABA.

Define redirect URLs, scopes and webhook endpoints.

Authorize a tenant

The organization grants your application access to a connection.

Call the API

Send messages and read resources with a scoped key.

Consume events

Verify signatures, deduplicate by event ID and acknowledge quickly.

POST /messages/template

202 Accepted

send-template.sh

curl -X POST https://connectapi.clickmaker.in/api/v1/messages/template \
  -H "Authorization: Bearer cmc_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: booking-8842" \
  -d '{
    "phoneNumberId": "pn_01J8XK4T",
    "to": "919876543210",
    "template": {
      "name": "appointment_reminder",
      "language": "en",
      "components": [{
        "type": "body",
        "parameters": [{ "type": "text", "text": "Ananya" }]
      }]
    }
  }'

Queued

accepted

Signed

HMAC-SHA256

Traceable

requestId

Example shape · endpoints marked planned are not yet available

Portals