Leads
Create Lead
Create a single lead for your campaign
POST
Endpoint Alias: You can also use
/api/v1/records instead of /api/v1/leads. Both endpoints are functionally identical - use whichever naming convention fits your integration.Lead Import Modes
The API supports two lead import patterns depending on your data availability:Standard Mode
Phone number known at import timeProvide
phoneNumber directly. The system will call this number when the lead is processed.Best for: CRM exports, contact lists, manual importsPrefetch Mode
Phone number fetched just-in-timeProvide
externalId only. The phone number is fetched from your CRM via a predial function before each call.Best for: CRM integrations where phone numbers change frequently or require real-time validationAt least one of
phoneNumber or externalId is required. You can provide both if you want to track the external reference alongside the phone number.Authentication
string
required
Your API key with
write scopeRequest Body
string
required
The ID of the campaign this lead belongs to
string
Lead’s phone number in E.164 format (e.g., +15555551234).Required if
externalId is not provided.string
Your CRM’s internal ID for this lead. Used for deduplication and prefetch lookups.Required if
phoneNumber is not provided.object
Custom data about the lead (name, company, notes, etc.)
string
ISO 8601 timestamp for when to call this lead
number
default:"0"
Lead priority (higher = called first). Range: 0-100
Response
boolean
Whether the request was successful
object
string | null
Error message if request failed
Examples
- Standard Mode
- Prefetch Mode
Phone number provided at import time:
Notes
Duplicate Prevention: Leads are deduplicated by
externalId first, then by phoneNumber. If a lead with the same identifier already exists in the campaign, the request will fail.