Leads
Create Lead
Create a new lead with optional checklist item updates
POST
This endpoint creates a new lead. You can pass lead-level fields (firstName, lastName, email, etc.) and optional checklist item updates by code. A single API_ACTIVITY action log is written for “Lead created” with all updates grouped in the timeline.Documentation Index
Fetch the complete documentation index at: https://docs.getomni.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
Requires thex-api-key header with a valid workspace API key.
Request Body
Lead first name
Lead last name
Lead email address
Lead phone number (formatted or raw; stored in E.164 when possible)
Lead middle name
Business name
External identifier for the lead (e.g. from a CRM system)
IANA timezone identifier (e.g. “America/New_York”). If not provided and a
phone number is given, the timezone is inferred from the area code.
Who handles the lead: “agent” (AI) or “manual” (human)
When true, marks the lead as opted out and sets optOutAt to the current time.
When true, sets emailVerifiedAt to the current time (marks the lead’s email as
verified).
Array of checklist updates. Each item:
{ "code": string, "value"?: any, "status"?: "TODO" | "COMPLETED" | "INVALID" | "SKIPPED" | "NEEDS_REVIEW" }. Use the checklist item code from your workspace.Set lead tags. Matching is case-insensitive, so “VIP” and “vip” are treated as
the same tag. Tags are created automatically the first time a name is used.
Pass [] to remove all tags.
Response
Whether the request succeeded
The created lead record. Includes: id, activitySummary, assigneeType,
businessName, createdAt, deletedAt, didOptOut, optOutAt, email,
emailVerifiedAt, externalLeadId, externalPortalLink, firstName, lastName,
phoneNumber, phoneVerifiedAt, source, tags, updatedAt, website.
Full checklist for the lead, grouped by checklist group. Each group includes
id, name, conditions, and an items array. Each item includes id,
checklistItemId, value, status, itemOverride, and a nested checklistItem with
code, label, fieldType, conditions, validationRules, etc. File-type items
include a documents array with presigned URLs.
Recent action logs for the lead (up to 100), enriched with tool info,
messages, and document presigned URLs.
Leads that share the same phone number or email (empty for test leads).
The most recent completed outbound message or follow-up action log, including
associated tool calls.
The next pending follow-up message action log, if any.
The next message awaiting approval, if any.