Posting Specifications
Transport
POST with either application/json or application/x-www-form-urlencoded. Both are accepted; JSON is recommended.
Authentication
The campaign key can be supplied three ways:
- In the URL:
POST /api/v1/lead/{seller_campaign_key} - As a field named
SELLER_CAMPAIGN_KEY - In the JSON body under the same key
Common fields
| Field | Format | Notes |
|---|---|---|
first_name |
text | |
last_name |
text | |
email_address |
Validated for deliverability signals | |
phone_home |
10 digits | Normalised to E.164 |
address |
text | |
city |
text | |
state |
2-letter | |
zip |
5 digits | |
ip_address |
IPv4/IPv6 | Used for fraud and proxy signals |
Required fields vary by vertical. Your campaign's specification lists exactly which are mandatory.
Consent fields
Where TCPA consent applies, submit the consent text shown to the consumer, the timestamp, the originating IP, and the source URL. These are stored per lead and are your evidence if a submission is later disputed.
Validation failures
A 400 response lists the fields that failed and why. Validation runs before distribution, so a malformed lead never reaches a buyer.
Rate limits
Submission is limited per campaign key. Exceeding it returns 429. Contact us before ramping volume significantly.