WhatsApp Platform API
Send and receive WhatsApp from your app, your workflow tool or your AI agent — one API key, one Authorization header.
WASync exposes WhatsApp connections as a plain REST API, a remote MCP server and an n8n node. Authenticate with an API key, then list connections, read messages and send WhatsApp messages — from any app or agent, with or without Bitrix24.
Base URL https://developers.wasync.app/api/v1.
Quickstart
Key, first call, first message. Under five minutes.
n8n
Install the community node and build a workflow.
MCP
Point Claude or Cursor at the remote MCP server.
API Reference
Every endpoint, generated from the OpenAPI contract.
Two credential types, one header
An API key is for automating your own account — that is most
integrations, and it is what these docs assume. OAuth2 is for an app that
other WASync customers install, where a third party has to consent to
connections they own; it has its own guide. Both go in
Authorization: Bearer … and both reach every endpoint.
Two connection types, one API
A qr connection is an ordinary WhatsApp number paired by scanning a QR
code (or typing a pairing code) — created and managed entirely through the API,
with no Meta Business account. A cloud_api connection is a WhatsApp
Business number registered with Meta. Both send and receive through the same
endpoints; the differences that matter are collected under
Connection types.
Building with an AI coding agent?
Give it https://developers.wasync.app/llms-full.txt — the complete machine-readable contract in one file: endpoints, auth, error catalog, idempotency rules, webhook schema and integration recipes. Every page here also has a Copy page for AI button.
Support is written-only: email and chat.