Custom data assigned

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

Custom data was added to a conversation or contact.

Use custom.data.assigned to react to a custom-field assignment, such as a subscription plan being stored. data.custom_data contains the field name and value; the example assigns enterprise to the plan field. Read data.assigned_by to identify the actor. Subscribe to Custom data removed for removals. For label-based classification, such as VIP, use Tag assigned.

For signature verification and retries, see Webhooks overview.

postWebhookcustom.data.assigned

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 custom.data.assigned.

occurred_atstring date-time required

When the business event occurred.

versionstring required

Payload schema version.

Example payload

{
  "id": "evt_1234567890abcdef1234567890abcdef",
  "event": "custom.data.assigned",
  "data": {
    "conversation": {
      "id": "0f46c0a1-8938-40e3-b2b5-bb56f569fcab",
      "channel": "website",
      "status": "open",
      "widget_name": "Main site widget",
      "identifier": "eouqtiupanm6uvglwshy"
    },
    "visitor": {
      "id": "9b0c5fe6-35ad-459d-b6ba-4288191f84f1",
      "name": "John Doe",
      "email": "john@example.com",
      "phone": "+1XXXXXXXXXX"
    },
    "custom_data": {
      "plan": "enterprise"
    },
    "assigned_by": {
      "automation": {
        "id": "c3d327ab-3ef6-4d19-8ee1-11b06c912cd6",
        "name": "Assign Sales Agent"
      }
    }
  },
  "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.