---
title: "Conversation created"
method: POST
path: "conversation.created"
---

# Conversation created

`POST conversation.created` (webhook)

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

A new chat has started.

Use conversation.created to open a corresponding support ticket or start tracking a new chat. Store `data.conversation.id` as the conversation identifier and `data.visitor.id` as the contact identifier in your integration. To retrieve the transcript, use the conversation ID with [List Conversation Messages](https://developers.chatway.app/operations/api-docs.conversations.messages). Subscribe to [Message received](https://developers.chatway.app/webhooks/webhook.message_received) for incoming messages and [Contact created](https://developers.chatway.app/webhooks/webhook.contact_created) for contact creation or identification. These events support different parts of the workflow.

For signature verification and retries, see [Webhooks overview](https://developers.chatway.app/webhooks/guides.webhooks_overview).

## Headers

- `X-Chatway-Event` string, required
- `X-Chatway-Webhook-Id` string, uuid, required
- `X-Chatway-Delivery-Id` string, required
- `X-Chatway-Delivery-Attempt` string, required
- `X-Chatway-Timestamp` string, required
- `X-Chatway-Signature` string, required

## Payload

- object
  - `id` string, required: Stable event ID (`evt_…`). Same across HTTP retries for this notification.
  - `event` string, required: Event name. For this webhook, always `conversation.created`.
  - `data` object, required: Payload for conversation.created.
    - `conversation` object, required
      - `id` string, uuid, required: Conversation ID.
      - `channel` string, required: Normalized channel.
      - `status` string, required: Conversation status.
      - `widget_name` string: Present when the conversation is tied to a website widget.
      - `identifier` string: Widget identifier when widget_name is present.
      - `created_at` string, date-time
      - `first_page_url` string
    - `visitor` object, required
      - `id` string, uuid, required: Visitor/contact ID.
      - `name` string: Visitor name. Omitted when empty.
      - `email` string, nullable, required: Visitor email. Always present; null when unknown.
      - `phone` string, nullable, required: Visitor phone. Always present; null when unknown.
      - `country` string: Visitor country code (for example US). Omitted when unknown.
      - `ip` string: Visitor IP address. Omitted when unknown.
      - `first_page_url` string: First page the visitor viewed. Omitted when unknown.
  - `occurred_at` string, date-time, required: When the business event occurred.
  - `version` string, required: Payload schema version.

## Acknowledgement `200`

Return any 2xx status to acknowledge receipt.

## Other responses

- `410`: Optional HTTP 410 Gone to signal the endpoint is permanently unavailable. Like every non-2xx response below 500 (including `408` and `429`), it is not retried. It does not disable the subscription; turn the webhook off in Chatway Settings if you want deliveries to stop.

---

[API](https://skmtc.dev/chatway/apis/chatway-developer-docs.md) · [All operations](https://skmtc.dev/chatway/apis/chatway-developer-docs/llms.txt) · [OpenAPI document](https://skmtc.dev/chatway/apis/chatway-developer-docs/revisions/ca1a1da291cc?raw)