---
title: "Identify Visitor"
method: POST
path: "/api/livechat/public/{widget_key}/identify"
tags: ["livechat", "livechat"]
---

# Identify Visitor

`POST /api/livechat/public/{widget_key}/identify`

## Request

- Base URL: `https://api.dialogbrain.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.dialogbrain.com/api/livechat/public/{widget_key}/identify`
- Auth: none declared. Required headers: `X-Session-Token`

Identify visitor with name/email/phone.

Updates entity and creates/links person record for unified contact management.
Uses same normalization as other channels (Telegram, WhatsApp) to enable
cross-channel contact linking.

Matching priority:
1. Phone match first (if provided)
2. Email match second (if no phone match)
3. Create new person if no match

## Path parameters

- `widget_key` string, required

## Headers

- `X-Session-Token` string, required

## Request body

- IdentifyRequest: Request to identify visitor. `identity_hash` is a v1 scaffold for HMAC-signed identity (Intercom-style): the field is accepted and stored on the visitor record, but server-side HMAC validation is deferred. v1 always returns `verified: false`.
  - `name` string, nullable
  - `email` string, email, nullable
  - `phone` string, nullable
  - `custom_data` object, nullable
  - `identity_hash` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway.md) · [All operations](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway/llms.txt) · [OpenAPI document](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway/revisions/77bef09a9209?raw)