whatsapp_accounts

Triggered when a WhatsApp account is successfully connected for a workspace user.

postWebhookwhatsapp_account:connected

Headers

X-TL-Partner-Idstring required

The unique identifier for the partner.

X-TL-Signaturestring required

a JSON Web Token (JWT) token that contains the partner_id, nbf (not before), and exp (expiration) fields. using the partner''s shared secret and can be used to verify authenticity and integrity.

Payload

workspace_idstring required

Identifier of the workspace where the WhatsApp account was connected / disconnected.

event_type'whatsapp_account:connected' | 'whatsapp_account:disconnected' required

Partner webhook event name.

partner_idstring required

Unique identifier of the partner that owns the workspace.

triggered_atstring date-time required

Timestamp when the event was triggered.

whatsapp_account_idinteger required

Internal WhatsApp account identifier.

phone_number_e164string required

Phone number associated with the WhatsApp account in E.164

user_idinteger required

Identifier of the user in the workspace who owns the WhatsApp

disconnected_atstring date-time

Example payload

{
  "workspace_id": "my-workspace",
  "event_type": "whatsapp_account:disconnected",
  "partner_id": "partner_12345",
  "triggered_at": "2024-01-01T12:00:00Z",
  "whatsapp_account_id": 67890,
  "phone_number_e164": "+123456789",
  "user_id": 98765,
  "disconnected_at": "2024-01-01T12:00:00Z"
}

Response

Receiver accepted the event

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.