The Create Form API is designed to enable seamless lead form creation and submission. It is ideal for capturing user data directly from landing pages or campaign websites, ensuring that lead information is collected accurately and efficiently.
{source-unique-id} with the unique link ID assigned to your campaign source (found in your posting spec).
Authorization header:
| Parameter | Type | Required | Description |
|---|---|---|---|
source-unique-id | string | Yes | The unique link identifier for the campaign source |
| Parameter | Type | Required | Description |
|---|---|---|---|
first_name | string | Conditional | Consumer’s first name |
last_name | string | Conditional | Consumer’s last name |
email | string | Conditional | Consumer’s email address |
mobile | string | Conditional | 10-digit mobile number (digits only) |
address | string | Conditional | Street address |
city | string | Conditional | City name |
state | string | Conditional | State abbreviation (e.g. CA) |
zip_code | string | Conditional | 5-digit ZIP code |
country | string | No | Country code (default: US) |
date_of_birth | string | No | Date of birth (YYYY-MM-DD) |
transaction_id | string | No | Pre-generated transaction ID; one is created if omitted |
sub1 – sub5 | string | No | Publisher sub-parameters for tracking |
adv1 – adv5 | string | No | Advertiser sub-parameters |
utm_source | string | No | UTM source |
utm_medium | string | No | UTM medium |
utm_campaign | string | No | UTM campaign |
utm_term | string | No | UTM term |
utm_content | string | No | UTM content |
gclid | string | No | Google Click ID |
fbclid | string | No | Facebook Click ID |
ttclid | string | No | TikTok Click ID |
jornaya | string | No | Jornaya lead ID token |
xxTrustedFormCertUrl | string | No | TrustedForm certificate URL |
tcpa_consent | string | No | TCPA consent flag |
tcpa_consent_date | string | No | TCPA consent timestamp |
| HTTP Code | Lead Status | Description |
|---|---|---|
| 201 | accepted | Lead was accepted and distributed |
| 201 | unsold | Lead was recorded but not distributed (e.g. duplicate, cap reached) |
| 400 | missingField | One or more required fields are absent |
| 400 | invalidField | One or more fields failed format validation |
| 400 | rejected | Lead was rejected by the campaign rules |
| 401 | rejected | Invalid or missing authorization token |
| 405 | rejected | HTTP method not allowed |
| 500 | rejected | Internal server error |
555-123-4567 or (555) 123-4567 both work.isDeDupe flag in the response indicates whether this lead was seen before.redirect_url from the response to forward the consumer to a thank-you page or offer wall.loan_amount, home_owner) may be required. Check your posting spec for the complete field list.429 Too Many Requests response.Your campaign unique ID
Lead details to add to the campaign
Lead's Transaction ID, Which was generate from click script of Pingtree
First name of the lead
Last name of the lead
Email of the lead
Mobile of the lead
Address of the lead
State of the lead
City of the lead
Zip Code of the lead
Date of Birth of the lead
Lead successfully updated
Status code of API response
Type of API response which can be success or error
Message of API response
Flag for dedup which confirms that lead is duplicate or not
Current status of lead which can be sold or unsold or new
Response Redirect URL of API response
Buyer response type for lead sold
Current buyer name for lead sold
Entire buyer response which we get from buyer's endpoint