Skip to main content
POST
Create or attach lead

Authorizations

Authorization
string
header
required

Use Authorization: Bearer tc_live_xxxxx

Body

application/json
name
string
required
Minimum string length: 1
phone_number
string
required

Phone number in E.164 format (also validated as dialable; country codes that don't exist are rejected)

Pattern: ^\+[1-9]\d{8,14}$
list_id
string<uuid>
required
email
string<email>
status
enum<string>
default:New
Available options:
New,
Contacted,
Converted,
Unsubscribed
notes
string
notes_append
string
tags
string[]
metadata
object

Response

Existing lead attached to the requested list (idempotent)

Result of POST /v1/leads. existed=false (returned with HTTP 201) means the phone number was new and a fresh lead row was created. existed=true (returned with HTTP 200) means a lead with this phone number already existed in the account; it has been (idempotently) attached to the requested list, and list_ids reflects every list the lead is currently in. The lead's other fields (name, email, notes, tags, metadata) are NOT overwritten on the attach path - use PATCH /v1/leads/{id} for that.

id
string<uuid>
required
account_id
string<uuid>
required
name
string
required
phone_number
string
required
Pattern: ^\+[1-9]\d{8,14}$
status
enum<string>
required
Available options:
New,
Contacted,
Converted,
Unsubscribed
tags
string[]
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
existed
boolean
required

false if a new lead was created; true if an existing lead was attached.

email
string<email> | null
notes
string | null
metadata
object
converted_at
string<date-time> | null
list_ids
string<uuid>[]