Skip to main content
POST
Create Lead
Creates a new lead deal record in your workspace.

Stage assignment behavior

When creating a lead, supply the target stage name in the stage_name body field (for example, "stage_name": "New Lead").

Attribution and custom fields

You can pass Meta campaign attribution fields inside meta_attribution (utm_source, utm_medium, utm_campaign) and custom field values defined for leads inside custom_fields.

Required permissions

Requires an API key with the crm:write scope.

Authorizations

x-api-key
string
header
required

Workspace API key header. The key implicitly determines your workspace isolation. Scopes: crm:read for GET/HEAD/OPTIONS, crm:write for POST/PATCH/PUT/DELETE.

Body

application/json
name
string
required

Lead title or organization name

Example:

"Acme Corp Enterprise Deal"

email
string<email>
Example:

"lead@acmecorp.com"

phone
string
Example:

"+15559876543"

pipeline_id
string

Optional pipeline identifier; defaults to primary pipeline if omitted

Example:

"pipe_default"

stage_name
string

Name of the target stage when creating the lead (e.g. 'New Lead', 'Qualified')

Example:

"New Lead"

assigned_to
string

Team member user ID

Example:

"user_sarah"

tags
string[]
Example:
custom_fields
object
Example:
meta_attribution
object

Response

Lead created successfully

Standard envelope returned by POST, PATCH, PUT, and DELETE (mutation) endpoints

success
boolean
required
Example:

true

data
object
required

The created or updated entity

error
null
required
Example:

null