Messaging

All messaging calls are on https://backend-dev.wabsync.com/api/v1 and require a session in ready status (see Sessions).

Send a message

POST /sessions/{sessionId}/send-message

curl -X POST "https://backend-dev.wabsync.com/api/v1/sessions/{sessionId}/send-message" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "212612345678",
    "type": "text",
    "content": "Hello from WabSync"
  }'

Common body fields

Field	Notes
`phone`	Digits with country code, no `+`
`type`	e.g. `text`, `image`, `file`, `audio`, `video`, `location`, `url`
`content`	Text string or structured content depending on `type`
`file`	Optional media descriptor (`url`, `mimetype`, `filename`)
`location`	Optional `latitude` / `longitude`

Exact enums and schemas: API reference.

Mark as seen

POST /sessions/{sessionId}/send-seen with phone and message_id.

Chat state (typing / recording)

POST /sessions/{sessionId}/send-chat-state with phone and state (typing or recording).

Inbound vs outbound

Outbound — your app calls /api/v1 as above.
Inbound — WhatsApp messages to the linked phone are delivered to your webhook URL (not polled on /api/v1). Configure that in the dashboard; see Webhooks.

There is no separate “message delivery ack” webhook today — use your own logging on send responses and inbound webhook payloads.

Getting started

Platform

Send a message

Common body fields

Mark as seen

Chat state (typing / recording)

Inbound vs outbound

​Send a message

​Common body fields

​Mark as seen

​Chat state (typing / recording)

​Inbound vs outbound

Send a message

Common body fields

Mark as seen

Chat state (typing / recording)

Inbound vs outbound