Skip to main content
POST
Create a lead

Authorizations

Authorization
string
header
required

Your API key, created in the Leadey dashboard under Settings → API Keys. Send it as Authorization: Bearer leadey_sk_live_….

Body

application/json
name
string
required

The person's full name.

email
string<email>

Work email address.

phone
string

Phone number in E.164 format.

linkedinUrl
string

Their LinkedIn profile URL.

company
string

Company name.

title
string

Job title.

campaignId
string

Add the lead straight into this campaign.

source
string

Where the lead came from. Shows in the Cockpit and can be filtered on with GET /leads?source=. Defaults to api.

customFields
object

Custom field values, keyed by field key. A field that doesn't exist yet is created automatically, so a migration doesn't have to pre-declare its columns — which makes this the place to park foreign identifiers such as a record id from your previous CRM.

Keys are slugified (Legacy Record ID is stored as legacy_record_id), and the response echoes the canonical keys so you can see exactly what landed. Values are stored as text; numbers, dates and booleans are coerced.

Example:

Response

This person was already in the workspace. The existing lead is returned unchanged.

data
object
required