Skip to main content
WEBHOOK

Headers

webhook-id
string
required

ID of the event, the same as id in the body. It's the same on every delivery attempt and is part of the signed content.

Pattern: ^evt_[0-9a-f]{32}$
webhook-timestamp
integer<int64>
required

Time this attempt was sent, in Unix seconds. It's part of the signed content and changes on every attempt. Reject a request whose timestamp is more than 5 minutes away from your clock.

webhook-signature
string
required

Space-separated signatures, each v1, plus the Base64 HMAC-SHA256 of webhook-id, webhook-timestamp, and the raw body joined by periods. The key is the Base64-decoded secret without whsec_.

Pattern: ^v1,[A-Za-z0-9+/]{43}=( v1,[A-Za-z0-9+/]{43}=)*$

Body

application/json

The event Wavix posts to your webhook URL.

Event of type whatsapp.sender.connected. One of your senders can send messages within its messaging limit, for example after registration or when a restriction ends. Posted to your webhook and returned by List WhatsApp events.

id
string
required

Unique ID of the event. It's the same on every delivery attempt and in the event list, so use it to discard duplicates.

Pattern: ^evt_[0-9a-f]{32}$
Example:

"evt_9e1a3c5e7a9c4e1a3c5e7a9c1e3a5c7e"

type
string
required

Type of the event, always whatsapp.sender.connected.

Allowed value: "whatsapp.sender.connected"
Example:

"whatsapp.sender.connected"

timestamp
string<date-time>
required

When Wavix detected the change, in ISO 8601 UTC with 6 fractional digits (microseconds). It isn't the delivery time in the webhook-timestamp header.

Example:

"2026-10-21T09:20:10.000000Z"

data
WhatsAppSenderEventData · object
required

Data of a sender event. It carries the sender's status and quality rating after the change, and the previous value of the attribute that changed.

Response

200

Your server acknowledges the event. Any 2xx status counts as delivered.