WhatsApp Business | Operate As Docs

Website: business.whatsapp.com
Connects by: Signing in with Meta
Category: Chat
Part of: Meta
Tools: 4

Service	Key	Base URL
WhatsApp Business	`whatsapp`	`https://graph.facebook.com/v23.0`

Connecting

Your client presses Connect on their link and approves on Meta's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "whatsapp"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "whatsapp"    ]  }]

Permissions

What the client reads	Permission it asks for
See the business accounts your WhatsApp numbers belong to	`business_management`
See and manage your WhatsApp numbers and message templates	`whatsapp_business_management`
Send and receive WhatsApp messages as your business	`whatsapp_business_messaging`

Tools

Install WhatsApp Business's typed package for your language:

pip install operate-as-whatsapp

pip install operate-as-whatsapp

Run whatsapp.create_message_template

curl -X POST https://api.operate.as/v1/actions/whatsapp.create_message_template \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "waba_id": "<waba_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/whatsapp.create_message_template \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "waba_id": "<waba_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/whatsapp.create_message_template

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://graph.facebook.com/v23.0. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../whatsapp/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../whatsapp/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Meta refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Meta access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Meta access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "meta",
    "services": [
      "whatsapp"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "meta",    "services": [      "whatsapp"    ],    "reconnectUrl": "https://…"  }}