Match Prospects
Prospects
Match prospects
Match a list of prospect attributes to Prospect IDs. Returns a list of the same length and order as the input list, with the matched IDs.
POST
Match Prospects
Introduction
The Match Prospects endpoint allows users to accurately match individual prospects to unique Prospect IDs using multiple fetchers, such as email, phone number, LinkedIn profile, or name and company combination. This ensures accurate lead identification and enhances sales and marketing workflows. Key Benefits:- Match and validate lead data across multiple fetchers.
- Enhance B2B prospecting by linking leads to business profiles.
- Improve lead scoring and segmentation with high-quality matches.
- Reduce data duplication and inconsistencies.
Endpoint: POST /v1/prospects/match
How Matching Works: The Waterfall
Matching is not a single lookup — each record you send runs through a sequential matching waterfall. Identifiers are attempted in a fixed priority order, from the most reliable to the least. As soon as a record matches at a step, it is resolved and removed from the waterfall; later steps only apply to records that are still unmatched.business_id is supplementary context, not a required identifier. When provided, it is applied at every waterfall step to scope the match to a specific company, which improves precision. It is never used to match a prospect on its own.- If a record contains multiple identifiers (e.g., both
linkedinandemail), it is matched at the highest-priority step that succeeds — in this example, LinkedIn is attempted first, and email is only tried if the LinkedIn match fails. - Each record is matched at most once. Once matched, it does not continue to lower-priority steps.
- Adding
business_idnever hurts — it refines every step it participates in.
How It Works
How It Works
- Input: Provide a list of prospects with at least one fetcher (e.g., email, phone number, LinkedIn URL, or name & company).
- Processing: Each record runs through the matching waterfall described above — identifiers are attempted in priority order (LinkedIn → email → phone → name & company → name & business ID), and a record exits the waterfall as soon as it matches.
- Output: A structured response with matched Prospect IDs, maintaining the same order as the input list. Records that cannot be matched return
prospect_id: null.
Request Schema
Request Schema
Example Request (cURL)
Example Request (cURL)
Bash
Example Response
Example Response
Note the fourth record: it contains only
full_name, so it never enters any waterfall step and returns prospect_id: null.JSON
Best Practices
Best Practices
- Provide the strongest identifier you have. LinkedIn URLs match with the highest confidence, followed by email and phone. Name-based matching is the last resort in the waterfall.
- Use multiple fetchers whenever possible — the waterfall automatically uses the highest-priority one that succeeds.
- Combine with
business_idto refine matches to a specific company — it improves precision at every step, and it is required for matching onfull_namewithout acompany_name. - Never send
full_namealone — it will always returnnull. Pair it withcompany_nameorbusiness_id. - Ensure accurate and up-to-date data for improved results.
- Handle
nullvalues in responses where no match is found. - Use the input field when sending multiple queries to match your queries with the results.
Authorizations
Body
application/json
Response
Successful Response
This is base response model for all responses in partner service.
The total_results number matched prospects
The total number of matches.
Required range:
x >= 0A list of matched prospects ids represented by MD5 hashes. May contain None for unmatched items.
- ProspectMatchOutputWithError
- ProspectMatchOutput