Create a lead record from intake payload
Creates a source-authenticated lead from a flat intake payload, capturing contact fields, metadata, and automation-ready lead details.
Query Parameters
The Leadping source key supplied as a query string parameter, or omitted when supplied as Authorization: Bearer lp_src_...
Body
The common lead fields submitted by the external system.
Request schema for the Leadping API lead intake request, including the fields clients can send.
First name of the lead, user, or contact represented by this lead intake request.
Last name of the lead, user, or contact represented by this lead intake request.
Email address for the person represented by this lead intake request.
Phone details for the lead, user, or business represented by this lead intake request.
Source-provided phone type, such as mobile, landline, or VoIP, used during lead intake normalization.
Lead date of birth supplied by intake sources and normalized into the lead profile.
Lead birth date used for demographic matching and insurance intake workflows.
First street address line submitted by the lead intake source.
Second street address line submitted by the lead intake source.
City for the lead or business postal address.
State, province, or region for the lead or business postal address.
ZIP code submitted by the lead intake source.
Postal code for the lead or business address.
Lead gender supplied by intake sources and normalized when possible.
Affiliate or publisher sub ID captured for lead attribution.
Seller-provided lead identifier used to deduplicate and reconcile lead delivery.
Alternate seller-provided lead identifier used during intake normalization.
Direct-post price supplied by the lead source during intake.
^-?(?:0|[1-9]\d*)(?:\.\d+)?$Lead price or transaction price supplied to the Leadping API.
^-?(?:0|[1-9]\d*)(?:\.\d+)?$UTM source parameter captured for lead attribution reporting.
UTM medium parameter captured for lead attribution reporting.
UTM campaign parameter captured for lead attribution reporting.
UTM term parameter captured for lead attribution reporting.
UTM content parameter captured for lead attribution reporting.
Product or offer associated with the lead or source.
Industry vertical used for lead routing, compliance review, and reporting.
Referring page or traffic source that sent the lead into Leadping.
Landing page URL where the lead submitted their information.
TrustedForm certificate URL used as proof of consumer consent.
External system identifier used to reconcile this lead intake request across integrations.
Source-provided key-value metadata retained for lead attribution and integration troubleshooting.
Tag IDs assigned to or filtered against this lead.
Tag names assigned to this lead when matching existing tags by name.
Response
The lead response was created successfully.
Response schema for the Leadping API lead response returned to authenticated clients.
Structured metadata used for attribution, integrations, and reporting on this lead response.
Contact details for the lead or customer represented by this lead response.
Canonical phone identity and provider lookup details for this lead.
Demographic profile details for the lead represented by this lead response.
Indicates whether this lead response is active and available in the Leadping API.
UTC timestamp when this record was archived.
User ID of the person who archived this record.
Defines why a lead was removed from the active working pipeline.
0, 1, 2, 3, 4, 5, 6, 7, 8, 9 Optional note explaining why the lead was archived.
Indicates whether the lead has been archived in Leadping.
Current disposition summary that describes the lead outcome.
Tags currently attached to this lead, source, or record.
The unique identifier for the entity.
The date and time when the entity was created.
The date and time when the entity was last modified, if applicable.

