Authentication
Jawib authenticates API requests using a Bearer token. A key identifies one data boundary and carries an explicit set of permissions, called scopes.
Authorization: Bearer jwb_…
Accept: application/json
Key types
| Key owner | Purpose | Data boundary |
|---|---|---|
| Partner company | Create customers, issue or revoke customer keys, and manage customer status. | The company management API. It does not automatically grant access to customer conversations or connections. |
| Partner customer | Connect the customer's number, send messages, read conversations, and manage webhooks. | That customer's resources only, subject to the key's scopes. |
| Direct company | Use WhatsApp for the company's own business. | The company's own resources. Direct companies cannot create partner customers. |
Issue and store keys
Create company keys in the partner dashboard's integration settings. Issue customer keys through the customer management API or the customer's dashboard controls. A customer token is returned once, at creation. Each customer may have up to five non-revoked keys.
Keep tokens in your application's backend, encrypted at rest. Never put a company or customer token in browser code, a mobile application, a public repository, or a URL.
Isolated application data
Store a mapping from your own customer ID to the Jawib customer ID, customer token, and connection ID. Your server chooses the customer's token for each request. End users see the pairing screen; they do not receive a company management key.
Scopes
Each endpoint lists its required scope. Group sending requires both messages:write and groups:write. Content access uses separate scopes for conversations, group messages, media, and participant receipts. A customer key cannot be granted partner-management or wildcard scopes.
Rotate or revoke a key
Issue a replacement key, update your backend, then revoke the previous key. Suspending a customer revokes their keys and disconnects their WhatsApp session. Re-enabling the customer requires a new key and a new pairing attempt.
Webhook signing secrets are separate from API tokens. Do not use an API token to verify webhook signatures.