About the project
Our client, a lead generation business, bought and sold leads across several sources and buyers. Leads were arriving in different formats, some had to be moved between systems by hand, and every new buyer meant another posting specification to work through. We built lead API integrations that receive leads from every source through one consistent process and post them to each buyer in the exact format that buyer expects.
The brief
- Accept leads automatically from forms, landing pages and outside vendors
- Post leads to multiple buyers, each with its own field names, formats and responses
- Stop incomplete and duplicate leads before they reach a buyer
- Send each lead to the right buyer based on its details
- Keep a record of every lead sent and every response, for disputes and reporting
What we delivered
- Lead receiving API: secure endpoints with separate credentials for each lead source
- Buyer posting: field mapping for each buyer’s specification, including JSON, XML and form posts
- Ping-post support: a two-step flow where buyers bid on partial lead data before the full lead is posted to the winner
- Validation and deduplication: required-field, format and duplicate checks on every lead
- Routing rules: leads sent to buyers based on the data they contain
- Full request logging: every post and buyer response stored with a timestamp, with retries for failed deliveries
How we built it
One way in, many ways out
Every lead, wherever it comes from, is converted into one standard format when it is received. Each buyer connection then maps that standard format to the buyer’s own specification. Adding a new buyer means adding one mapping, not changing how leads are received.
Reading buyer responses properly
Buyers reply in different ways: an accepted flag, a rejection reason, a duplicate notice or a price. The integration reads each buyer’s response so the client knows the outcome of every post immediately.
A record for every lead
Because the full request and response are logged, the client can answer a buyer’s dispute by showing exactly what was sent and when.
How it is offered
After building the lead API integration for this client, we made it available to other businesses as a ready product, configured for each one. It is offered as a monthly or annual subscription, or as a permanent license with a one-time payment.
Need to post or receive leads by API? See our lead API integration services, read our guide to lead posting and ping-post, or get in touch.
Ready to start your project?
Tell us about your goals and timeline. We'll follow up with next steps and a straightforward proposal — no pressure, no obligation.