Validate Every Lead.
Deliver on Your Schedule.
NexusLead takes the leads your vendors post, checks each one against the rules you set for its list, and delivers it to the buyers whose orders it matches — in real time, after a delay, or as a CSV file.
JSON or form posts • Every rejection says why • Real-time, delayed or CSV delivery
One Platform. From Post to Buyer.
Intake, validation, duplicate and suppression checks, distribution and reporting — set up per list and per order.
Real-Time Intake
Vendors post JSON or form fields to one URL with a list API key, send leads straight from a web form, or upload a CSV. Intake typically answers in 150–300 ms.
Per-List Validation
Phone numbers checked against the NPA-NXX exchange database. Email format, mail domain, disposable and role addresses. IP address checks. Fake names and profanity. Required fields. Each list has its own settings.
Duplicates & Suppression
Duplicate checks on email, phone or IP over the window you choose, within one list or across your lists. Suppression entries (email, phone, domain or IP) are checked at intake, and each buyer’s own suppression list before that buyer receives a lead.
Distribution Rules
Every buyer whose order matches receives the lead — or make orders exclusive and only one of them wins it. Orders choose leads by source list, state, daily and total caps, dedupe days and excluded email domains.
Delivery Options
Real-time HTTP posts to the buyer’s endpoint, with field mapping and authentication. Delayed delivery after 24 hours, 7 days or a custom delay. Or a CSV export for buyers who take files.
Reporting & Records
Dashboards count leads by vendor and list, intake outcomes, deliveries, the delivery queue and revenue by client. Intake posts are logged with the answer that was returned.
What Happens When a Lead Arrives
Each list has its own checks. A lead that fails one is refused, and the answer says which check failed and why — the same answer your vendor receives is kept in the post log.
POST /api/leads
x-api-key: <your list key>
fname=Jane&lname=Doe&email=jane@example.com&phone=212-555-0142
400 Bad Request
{
"error": "Phone uses reserved 555 prefix.",
"gatekeeper": "blocked",
"status": "rejected",
"checks": [
{ "name": "Phone Validation", "passed": false,
"error": "Phone uses reserved 555 prefix." }
],
"flags": []
}The response shape vendors receive, for a lead posted with a 555 number to a list with default settings.
From Vendor Post to Buyer
Every lead posted to a list goes through the same steps: validation → duplicate check → appended data → order matching → delivery. Which buyers get a lead is recorded before any delivery is attempted.
Moving From ListFlex?
NexusLead was built to run the same day-to-day list work. Here is what carries over, and what changes.
What carries over
- The field names vendors already post —
fname,lname,ip,date_subscribed,xxTrustedFormCertUrland other common variants map to standard fields - JSON or form-encoded posts, with the API key in a header or in the body
- Validation, duplicate windows, caps and required fields, set per list
- Custom fields you define, for every vertical or just one
- Delayed delivery: 24 hours, 7 days or a custom delay
- CSV export for buyers who take files
What changes
- Vendors post to a new URL, with a list key from NexusLead
- Buyers are set up as orders: source lists, states, caps and delivery timing
- Lead history does not move by itself — tell us what you need to bring over
Before You Ask
What is NexusLead?
A lead intake and distribution platform. Vendors post leads to a list by API; each lead is checked against that list’s rules, stored, and delivered to the buyers whose orders it matches — in real time, after a delay, or as a CSV export.
What happens to a lead that fails a check?
It is refused and never reaches a buyer. The answer to the post says which check failed and why, and the attempt is recorded with that reason.
Does NexusLead check the National Do Not Call Registry?
No. NexusLead does not scrub against the National Do Not Call Registry, and it is not a compliance service. It checks the suppression entries you load — at intake, and against each buyer’s own suppression list before that buyer receives a lead.
What consent records does NexusLead keep?
The consent fields your source sends — IP address, user agent, consent time and consent text — plus any TrustedForm, Jornaya or LeadCustody certificate, stored with the lead. A lead whose consent record is incomplete is flagged with what is missing.
How fast does intake answer?
Typically in about 150–300 ms, measured on production. The first post after a quiet period can take longer.
How is NexusLead priced?
We quote on your monthly lead volume; there are no published plans yet. Request access and tell us roughly how many leads you handle a month.
Tell Us Your Volume. We'll Quote.
There are no published plans yet. Request access with your approximate monthly lead volume and we'll reply by email with a price.
Request AccessSee If NexusLead Fits Your Lists
Tell us about your vendors, your lists and how your buyers take leads. We'll tell you plainly what NexusLead can do for them today — and what it can't.
Requesting access does not create an account or ask for payment details.