Contact updated

Incoming webhook deliveries are authenticated with HMAC signature headers (X-Chatway-Signature and X-Chatway-Timestamp), not your Chatway API key.

An existing contact was updated.

Use contact.updated to keep an existing CRM record synchronized. Find the record using data.contact.id, then inspect data.updated_fields and the matching entries in data.previous_values and data.current_values. For example, an email change should update the existing contact rather than create a second record under the new address. Use Get Chat Contact to retrieve a fresh profile and Contact created for the initial contact notification.

For signature verification and retries, see Webhooks overview.

postWebhookcontact.updated

Headers

X-Chatway-Eventstring required

Event name for this delivery.

X-Chatway-Webhook-Idstring uuid required

Unique webhook subscription ID.

X-Chatway-Delivery-Idstring required

Unique ID for this HTTP delivery attempt (del_ + 32 hex characters). A new value is sent on each retry.

X-Chatway-Delivery-Attemptstring required

Attempt number for this event (1 on first try). Sent as a decimal string in the header.

X-Chatway-Timestampstring required

Unix timestamp in seconds when the request was signed. Sent as a decimal string in the header.

X-Chatway-Signaturestring required

sha256= followed by the lowercase hex HMAC SHA256 of {X-Chatway-Timestamp}.{raw request body}, keyed with your webhook secret. The example is computed for the example body serialized as compact JSON, the example timestamp, and the placeholder secret whsec_exampleSecretForDocsOnly00000000.

Payload

idstring required

Stable event ID (evt_…). Same across HTTP retries for this notification.

eventstring required

Event name. For this webhook, always contact.updated.

occurred_atstring date-time required

When the business event occurred.

versionstring required

Payload schema version.

Example payload

{
  "id": "evt_1234567890abcdef1234567890abcdef",
  "event": "contact.updated",
  "data": {
    "contact": {
      "id": "9b0c5fe6-35ad-459d-b6ba-4288191f84f1",
      "name": "John Doe",
      "email": "john.new@example.com",
      "phone": "+1XXXXXXXXXX"
    },
    "updated_fields": [
      "email"
    ],
    "previous_values": {
      "email": "john@example.com"
    },
    "current_values": {
      "email": "john.new@example.com"
    }
  },
  "occurred_at": "2026-02-04T10:30:00Z",
  "version": "2026-09"
}

Response

Return any 2xx status to acknowledge receipt.

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.