Create an account and a key
An email and a password, then one API key. No redirect URI, no PKCE, no consent screen.
Go to https://developers.wasync.app/keys, create an account with an email and a password, and create a key. Give it a name, tick the scopes you need, and optionally restrict it to a set of IP addresses.
The key is shown once — only a hash of it is stored. Copy it into your environment straight away.
export WASYNC_API_KEY=wsk_live_…Send it on every request:
Authorization: Bearer $WASYNC_API_KEYThat is the whole auth setup. No redirect URI, no PKCE, no consent screen, no token refresh.
Scopes
Tick only what the integration needs — scopes are per key.
| Scope | What it allows |
|---|---|
whatsapp.read | List connections and read messages. |
whatsapp.send | Send messages and read receipts. |
whatsapp.events | Receive webhooks, and configure where they go. |
whatsapp.manage | Create, inspect, restart, log out and delete connections. |
Scopes and the reachable connection list are resolved live on every request, so revoking a key or narrowing it takes effect on the very next call — there is nothing cached and nothing to refresh. The details, and what each scope costs you if it leaks, are under Scopes.
You cannot lock yourself out
The optional IP allowlist is enforced on API calls only. The page where you edit it is authenticated by your account, not by the key, so it stays reachable from any address. See IP allowlist.
What a connection costs
Each WhatsApp number needs an active licence to send and receive. A new number
starts on a 7-day free trial, then $19 per number per month for a qr
(WAPP) number or $29 per number per month for a cloud_api (WABA) number, in
USD. On a Bitrix24 portal, API access to a number is a separate $12 per number
per month add-on. Licences & trial has
the full picture.