Skip to main content
PATCH
Reassign a lead to another user

Authorizations

x-api-key
string
header
required

Your workspace API key. Create one in Settings → API Keys; the plaintext value is shown once and never again.

Keys are scoped. A key needs conversations:send to send, conversations:read to read threads and messages, templates:read to list templates, and channels:read to list channels. A key missing the scope for an endpoint gets 403.

The CRM endpoints use the same resource:action form: leads:read, leads:create, leads:update, leads:delete, customers:read, customers:create, customers:update, customers:delete, customers:manage.

Several resources have no scope of their own and borrow one:

Grant only what the integration needs — a key that only sends notifications should hold conversations:send and nothing else.

X-Tenant-Id
string
header
required

Your workspace UUID. Required on every request in addition to x-api-key.

It does not select the workspace — data access is always scoped to the workspace that owns the API key, and a mismatched value cannot read anyone else's data.

Path Parameters

id
string<uuid>
required

Body

application/json
assigned_to_user_id
string<uuid>
required

Response

The reassigned lead.

id
string<uuid>
name
string
email
string
phone
string
company_name
string
status
string

The lead's stage key — see GET /v1/lead-stages.

customer_type
enum<string>
Available options:
individual,
business
industry
string
source
string

Where the lead came from, e.g. whatsapp or website.

assigned_to_user_id
string<uuid>
priority
enum<string>
Available options:
urgent,
high,
medium,
low
probability
integer

Percentage, 0–100.

value
number | null

Deal size.

currency
string
expected_close_date
string<date> | null
tags
string<uuid>[]
created_at
string<date-time>
updated_at
string<date-time>