LeadVettr
Integrations

Check every lead, however it reaches you.

Most buyers are set up in under 15 minutes without a developer. Pick the way your leads arrive today.

Call platformsRetreaver, TrackDrive, Ringba, CallGrid, CallScaler and Twilio check each caller while the phone rings. 40-second setup videos.Your lead platformLead Prosper, boberdoo, LeadsPedia and other ping/post systems call LeadVettr and block bad leads before you pay.Zapier & MakeScreen leads from Facebook Lead Ads, Google Sheets, forms or your CRM — no code.EmailForward lead emails to your private LeadVettr address. We read, score and save them.Upload a fileDrop today's leads in a spreadsheet and download them back with a verdict on every row.Your sellersGive each seller a key so they check leads with LeadVettr before delivering them to you.APIOne POST per lead, answers in about 150 ms. JSON or form fields.Before you bid (ping)Check a ping/post ping before you bid. Answers bid or pass. Pings are free.Results from HubSpotConnect HubSpot in one click. Sold, returned and no-contact results sync back every 30 minutes.

Call platforms

Pick your platform to watch the setup. Every call is checked while it rings, and rejected calls never reach a buyer. More detail on the pay-per-call page.

Set up the call check in Retreaver · 40 s · example data · presenter is AI-generated

Lead platforms

Lead Prosper can call LeadVettr as an API Filter and block leads before they reach you. No developer needed.

  1. In Lead Prosper open the campaign, supplier or buyer you want to protect, go to Filters, click Add+ and choose API Filters.
  2. Set the stage to POST (use PING only if the ping already carries the phone number).
  3. Post URL: https://leadvettr.com/_api/v1/score?source=leadprosper&format=text · Request Method POST · Payload Type FORM or JSON · HTTP Timeout 5 seconds.
  4. Headers: add Authorization with the value Bearer YOUR_API_KEY.
  5. Payload Body: map your campaign fields to first_name, last_name, phone, email, state, zip, ip_address, consent_cert_id (TrustedForm URL), lead_id, and the supplier name to seller.
  6. Response Mapping: Response Contains reject → Blocked. Add another for review if you'd rather block borderline leads too.
  7. Turn on Continue on request error for 5xx so a LeadVettr outage never stops your lead flow.
Settings
URL:        https://leadvettr.com/_api/v1/score?source=leadprosper&format=text
Method:     POST
Auth:       Header  Authorization: Bearer YOUR_API_KEY
            (or add &api_key=YOUR_API_KEY to the URL if headers aren't possible)
Body:       JSON or form fields: first_name, last_name, phone, email, state, zip, ip_address, form_duration_seconds, consent_cert_id (TrustedForm or Jornaya), date_of_birth, lead_id, seller, cost
            Common names like FirstName, phone_home, zipcode, xxTrustedFormCertUrl also work.
Response:   the word accept, review or reject (drop &format=text to get JSON with score and reasons)
Rule:       reject the lead when the response contains "reject" (optionally also "review")
Timeout:    5 seconds (typical response ~150 ms). If LeadVettr can't be reached, let the lead through.

Zapier & Make

Zapier

Send leads in (from Facebook Lead Ads, Google Sheets, forms, your CRM…)

  1. Create a Zap with your lead source as the trigger (e.g. Facebook Lead Ads › New Lead).
  2. Add the action Webhooks by Zapier › POST.
  3. URL: https://leadvettr.com/_api/v1/score?source=zapier · Payload Type json.
  4. Data: add rows first_name, last_name, phone, email, state, zip, seller (e.g. "Facebook") and map them to the trigger's fields.
  5. Headers: Authorization = Bearer YOUR_API_KEY.
  6. Add Filter or Paths on the Verdict field so only accepted leads go on to your CRM or dialer.

Get verdicts out (for leads that arrive any other way)

  1. Create a Zap with trigger Webhooks by Zapier › Catch Hook and copy its URL.
  2. Paste it into the Webhook tab here and switch it on. Every scored lead is sent there with its verdict.

Make (Integromat)

Send leads in

  1. After your lead-source module, add HTTP › Make a request.
  2. URL https://leadvettr.com/_api/v1/score?source=make, Method POST, Body type Raw, Content type JSON.
  3. Header Authorization: Bearer YOUR_API_KEY. Tick Parse response.
  4. Request content: a JSON object with first_name, phone, email, state, zip, seller… mapped from the previous module.
  5. Add a filter on data.verdict = accept before the next module.

Get verdicts out

  1. Start a scenario with Webhooks › Custom webhook and copy its address.
  2. Paste it into the Webhook tab here and switch it on.

Email

Every account gets a private address like lv1a2b3c…@in.leadvettr.com (under Connect › Email). Forward lead emails there, or ask sellers to copy it in. "Label: value" emails are read directly; free-form ones are read by AI. You can get an email back for flagged leads, every lead, or none.

Upload a file

Under Screen a file, upload an Excel or CSV file of fresh leads (up to 5,000 rows). LeadVettr matches your columns, scores every row, and gives you the same file back with leadvettr_verdict, leadvettr_score and leadvettr_reasons columns. Want to test first? Run a free back-test on last month's leads.

Not sure how to get the file out of your system? See the export guides for Lead Prosper, boberdoo, LeadsPedia, Salesforce, HubSpot, Velocify, Clio, Litify and Filevine.

Your sellers

Under Connect › Your sellers, create a key for each seller and we'll email them setup instructions. Their leads are checked before delivery and show up in your account tagged with their name. What sellers see.

API

POST https://leadvettr.com/_api/v1/score with Authorization: Bearer YOUR_API_KEY. Send JSON or form fields; get back verdict, score and reasons. Add ?format=text for just the verdict word. Report what happened later with POST /v1/outcome.

Webhook out

Turn on a webhook to receive every verdict — from any channel — in Zapier, Make, your CRM or your own server. Requests are signed with HMAC-SHA256.

Before you bid (ping)

On ping/post, the ping arrives before you see the full lead. Point your platform at POST https://leadvettr.com/_api/v1/ping with the same API key and whatever the ping carries: seller, state, ZIP, and a phone or email if your platform shares one. LeadVettr checks duplicates, blocked sellers, states you don't write in and the seller's return history, then answers bid or pass (add ?format=text for just the word). Pings aren't stored and aren't billed.

Send results back

Seller grades and return claims get better when LeadVettr knows what happened to each lead. Under Connect › Send results back, connect HubSpot in one click. Choose the field that holds your lead status, check how each value is read (sold, returned, contacted, no contact), and results sync every 30 minutes. LeadVettr only reads contacts and never changes anything in HubSpot.

Using another CRM? Upload a results file under Returns › Update results, or send them with POST /v1/outcome. Results are matched by phone or email, so you don't need LeadVettr's IDs, and your CRM's own labels ("Closed won", "Bad number") are understood.

Try it on last month's leads first — free.

Create a free account