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 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: The system cross-references internal datasets and returns the best possible matches.
- Output: A structured response with matched Prospect IDs, maintaining the same order as the input list.
Request Schema
Field | Type | Description |
---|---|---|
prospects_to_match: | Array | A list of prospect fetchers to match |
email | String | The prospect’s email address |
phone_number | String | The prospect’s phone number |
full_name | String | The prospect’s full name (must be accompanied by company_name ) |
company_name | String | The prospect’s company name (must be accompanied by full_name ) |
linkedin | String | LinkedIn profile URL |
business_id (optional) | String | Filters the match to a specific company |
Example Request (cURL)
Example Request (cURL)
Bash
Example Response
Example Response
JSON
Best Practices
Best Practices
- Use multiple fetchers whenever possible to increase match accuracy.
- Combine with
business_id
to refine matches to a specific company. - Ensure accurate and up-to-date data for improved results.
- Handle
null
values 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
Required range:
x > 0
The total number of matches.
Required range:
x >= 0
A list of matched prospects ids represented by MD5 hashes. May contain None for unmatched items.
- ProspectMatchOutputWithError
- ProspectMatchOutput