Webhooks

WabSync can notify your HTTPS endpoint when events happen on a linked session. You create webhooks in the dashboard (they are tied to your user account and a session). The external /api/v1 API does not include webhook CRUD — management is through the product UI / app API behind https://backend-dev.wabsync.com. Messaging and sessions for integrators stay on https://backend-dev.wabsync.com/api/v1.

What you should build

An HTTPS endpoint that accepts JSON POST (or the method you configured).
A webhook in the dashboard pointing at that URL, linked to a session.
Logic that handles inbound message payloads (below).
Separately, poll GET https://backend-dev.wabsync.com/api/v1/sessions/{sessionId} (or use the dashboard) for session status — status changes are not currently POSTed to customer webhook URLs.

When inbound webhooks fire

Condition	Behavior
Provider event is an inbound `message`	Eligible to forward
Session `status` is `ready`	Forwarded to active webhooks for that session
Session not `ready`	Not forwarded
Webhook not linked to the session	Will not receive traffic

Broadcast / status chat noise from the provider is ignored.

Payload your URL receives (inbound message)

WabSync transforms the provider event into a compact JSON body, for example:

{
  "sessionId": "123e4567-e89b-12d3-a456-426614174000",
  "messageId": "ABGGFlA5FpafAgo6EhQmJQ==",
  "timestamp": 1710000000,
  "from": "212612345678",
  "type": "text",
  "body": "Hello",
  "hasMedia": false,
  "mediaContent": null
}

Field	Meaning
`sessionId`	Your session UUID
`messageId`	Provider message id (useful for seen / dedupe)
`timestamp`	Event time from the provider
`from`	Sender phone digits
`type`	e.g. `text`, `image`, `file`, `audio`, `video`, `location`
`body`	Text / caption when present
`hasMedia`	Whether media is attached
`mediaContent`	Media metadata / URL payload when present

Respond quickly with 2xx. Retries are not guaranteed on failure; keep your handler idempotent using messageId.

Session status (not via webhook today)

Track pairing and health with the sessions API or dashboard. Status values:

Status	Meaning
`pending`	Waiting for initialization
`created`	Created; prepare to link
`scan_qr_code`	Scan the QR code
`authenticated`	Connected; preparing
`ready`	Can send/receive; inbound webhooks can fire
`stopped`	Paused
`disconnected`	Connection lost
`failed`	Failed — restart

Details: Sessions.

Practical checklist

Create session + reach ready (Quickstart).
Register webhook URL for that session in https://backend-dev.wabsync.com/app.
Send a WhatsApp message to the linked number and confirm your endpoint logs the JSON above.
Keep polling session status if you need lifecycle updates beyond inbound messages.

Questions? https://backend-dev.wabsync.com/contact

Getting started

Platform

What you should build

When inbound webhooks fire

Payload your URL receives (inbound message)

Session status (not via webhook today)

Practical checklist

​What you should build

​When inbound webhooks fire

​Payload your URL receives (inbound message)

​Session status (not via webhook today)

​Practical checklist

What you should build

When inbound webhooks fire

Payload your URL receives (inbound message)

Session status (not via webhook today)

Practical checklist