A posting key belongs to one lead source, like a vendor or another website. It can only add leads to that source. It can't read your leads, so giving one out is safe, and revoking it stops that vendor alone.
Make a posting key
Account admins: Team, API keys, New posting key.
- Pick the vendor's Source, or make a new one with its Cost per lead.
- Name the key and press Make key.
- Copy the key now. It's shown only once.
What to send the vendor
- The key (it starts
lv_post_). - The address to post to:
https://leadvault.com/api/v1/leads - The API docs: https://leadvault.com/api
Vendors can post JSON or a plain form post, and LeadVault forgives the usual spellings (any phone format, state names, "$350,000" or "350k", yes/no). A small example:
curl https://leadvault.com/api/v1/leads \
-H "Authorization: Bearer lv_post_..." \
-H "Content-Type: application/json" \
-d '{"type": "mortgage", "first_name": "Ana", "last_name": "Rivera",
"phone": "(310) 555-0123", "email": "ana@example.com", "state": "CA",
"answers": {"loan_purpose": "refinance", "loan_amount": "$350,000"},
"consent": {"text": "By clicking Get my quote, I agree...", "checked": true}}'GET https://leadvault.com/api/v1/lead-types lists each lead type's question keys and choices, so the vendor can match their fields.
What happens to the lead
It arrives under the key's source, at its type's first stage, and goes out by your distribution rules. Duplicates and do-not-contact people are kept and marked. The consent they send is saved with the lead.
Never let a vendor put the key in the address (?api_key=): LeadVault refuses it, since addresses end up in logs. It goes in a header, or as a form field named api_key.
Returns of bad leads can reach the vendor by themselves. See Duplicates and returns.
Didn't answer it? Ask us.