Skip to main content

API - Coexistence

The Coexistence API allows you to synchronize contacts and message history from your WhatsApp Business account to Positus programmatically. This is a quick reference of the synchronization endpoints.
API Base: https://api.positus.global/v2Authentication: All requests must include the Authorization: Bearer <your-token> header, where <your-token> is your workspace’s authentication token.

Synchronization endpoints


Synchronize contacts

POST https://api.positus.global/v2/whatsapp/numbers/{NUMBER_ID}/onboarding-smb-app/sync-contacts Requests synchronization of contacts saved in the WhatsApp Business app to your Positus account.

Parameters

Headers

Request Body

No request body is required for this request.

Behavior

Synchronization is asynchronous: the call only requests the start of the process. The import can be triggered only once per onboarding, within the 24-hour window after Coexistence activation.
Contact synchronization does not generate a webhook event. Positus processes the import internally and reflects the result directly on your account. Once complete, contacts become visible in the platform’s contact list and via the contacts API.

Response

After a successful call, the server responds with status 200 OK and starts the asynchronous process. There is no specific response body — monitor the appearance of contacts in your account.

Synchronize message history

POST https://api.positus.global/v2/whatsapp/numbers/{NUMBER_ID}/onboarding-smb-app/sync-message-history Requests synchronization of message history from your WhatsApp Business account to Positus.

Parameters

Headers

Request Body

No request body is required for this request.

Behavior

Synchronization is asynchronous: the call only requests the start of the process. The import can be triggered only once per onboarding, within the 24-hour window after Coexistence activation.

Message receipt

Synchronized messages arrive at your configured webhook in the { contacts, messages } format. Each message includes complete metadata: sender, recipient, content type, and timestamp.
The webhook payload follows the standard structure of Positus notifications, with the messages block containing all imported messages.

Context of use

During onboarding via Embedded Signup, Positus automatically triggers these synchronizations. These endpoints exist for cases where you need to manually request synchronization after the initial onboarding.
Also consult: