Filters prospects by country, company size, revenue, and more.
Returns minimal data needed for further filtering, deduplication, or record previews.
Introduction
The Fetch Prospects endpoint allows users to retrieve a list of prospect records based on filtering criteria such as job level, department, or other professional attributes. This API is essential for sales intelligence, lead enrichment, and prospecting workflows.
📌 Key Benefits:
- Identify high-value prospects based on job roles, seniority, and industry.
- Enhance lead scoring and segmentation with structured data.
- Retrieve up-to-date professional details to optimize outreach.
- Integrate seamlessly with existing CRM and marketing automation platforms.
- Consideration:
Not all filters have a high coverage rate. Using a filter with low data coverage may result in a smaller set of returned results. Conversely, using broader filters can yield more results. For example, if filtering by a very specific attribute results in few matches, expanding the filter criteria may increase the number of retrieved records.
Endpoint: POST /prospects
POST /prospects
How It Works
- Input: Provide filters such as job level, department, or industry to refine prospect search.
- Processing: The system scans and retrieves relevant prospect records.
- Output: A structured response containing matched prospect data.
Request Schema
Field | Type | Description |
---|---|---|
mode | String | full |
size | Number | Max number of returned results - up to 10000 |
page_size | Number | Max number of records per page - up to 100 |
page | Number | Page number to retrieve |
filters | Object | Filter object (see Filters Object below) |
Filters Object
Filters are provided in the request body inside the "filters"
key. Each filter has:
type
: the filter type (e.g.,includes, exists, range, any_match
).any_match
Filter Type :
Theany_match
filter returns results that contain all of the words specified in the input value, regardless of their order or position.
Example:- Filtering with
"VP of Sales"
will match titles like"VP of Sales and Marketing"
. - It will not match
"VP Sales"
because the word"of"
is missing.
Useany_match
when you want to match multi-word phrases more precisely.
Note that all words in the input must be present in the target field for a match to occur. values
orvalue
: the value(s) to filter by.
Example:
"filters": {
"company_size": {
"type": "includes",
"values": ["11-50", "51-200"]
}
}
Pagination Parameters
Data fetching supports pagination.
Use the following parameters to control pagination:
Field | Type | Description |
---|---|---|
size | Number | Maximum number of results to return (up to 10000) |
page_size | Number | Maximum number of records per page (up to 100) |
page | Number | Page number to retrieve |
Mode Parameter
The fetch endpoints support a mode
to define how much data to return:
Value | Description |
---|---|
full | Returns all available data for prospects |
Prospect Filters
Prospects Filter Reference
Parameter | Description | Notes / Best Practices |
---|---|---|
has_email | Filter prospects by whether they have an email. Categories: [True , False ] | |
has_phone_number | Filter prospects by whether they have a phone number. Categories: [ True , False ] | |
has_linkedin_profile | Filter prospects by whether they have a LinkedIn profile. Categories: [ True , False ] | |
job_level | Filter prospects by their job level. Categories: [director , manager , vp , partner , cxo , non-managerial , senior , entry , training , unpaid ] | Use this normalized field for consistent filtering across companies. |
job_department | Filter prospects by their job department. Categories: [customer service , design , education , engineering , finance , general , health , sales , ...] | Best used in combination with job_level to increase accuracy and generalize across different title variations. |
business_id | Filter prospects by account. Use Explorium entity IDs. Example: [ EXP_ENTITY_ID_1 , EXP_ENTITY_ID_2 ] | |
country_code | Filter prospects by country using alpha-2 codes. Example: [ us , ca ] | |
region_country_code | Filter prospects by region using ISO 3166-2 codes. Example: [ us-ut , us-ca ] | |
company_size | Filter by company’s number of employees. Options: [ 1-10 , 11-50 , ..., 10001+ ] | |
company_revenue | Filter by company’s annual revenue. Options: [0-500K , 500K-1M , ..., 10B-100B ] | |
google_category | Filter by company’s Google business category. Example: [ Paving contractor , Retail ] | |
naics_category | Filter by NAICS code (2, 4, or full). Example: [23 , 5611 ] | |
linkedin_category | Filter by company’s LinkedIn business category. Example: [ software development , investment banking ] | |
job_title | Filter prospects by their job titles. Example: [Sales Representative , SEO specialist , Technical Support Engineer ] | This field is not normalized, meaning job titles appear as free text and can vary widely between companies (e.g., "Sales VP", "VP of Sales", "Vice President - Sales"). Because of this, filtering by specific words or phrases may lead to incomplete or inconsistent results. For broader and more reliable coverage, we recommend using the normalized fields: - job_level (e.g., vp , director , cxo )- job_department (e.g., sales , marketing , engineering )These provide standardized classifications and allow for more consistent filtering across different organizations. |
company_country_code | Filter by company HQ country using alpha-2 codes. Example: [ us , ca ] | |
company_region_country_code | Filter by company HQ region using ISO 3166-2 codes. Example: [ us-ut , us-ca ] |
🎯 Prospecting HR Directors at Healthcare Companies in Texas for Payroll Software
🔍 Use Case:
A payroll software provider wants to sell to HR directors at mid-sized healthcare organizations in Texas who handle payroll compliance and workforce management.
📌 Filters:
- Company Country Code:
["us"]
- Company Region (State Code):
["us-tx"]
- Company Size:
["501-1000"]
- Company Revenue:
["75M-200M"]
- NAICS Category:
["62"]
(Healthcare & Social Assistance) - Job Level:
["director", "manager", "vp"]
- Job Department:
["human resources"]
- Has Email:
["True"]
🎯 Targeting CFOs of Investment Banks in New York for Financial Compliance Software
🔍 Use Case:
A regulatory compliance software provider wants to reach out to CFOs at mid-sized investment banks in New York who have been in their role for over two years and are likely leading compliance initiatives.
📌 Filters:
- Company Country Code:
["us"]
- Company Region (State Code):
["us-ny"]
- Company Size:
["1001-5000"]
- Company Revenue:
["500M-1B"]
- LinkedIn Category:
["investment banking"]
- Job Department:
["finance"]
- Job Level:
["CXO"]
- Has Email:
["True"]
- Has Phone Number:
["True"]
Example Request (cURL)
curl -X POST \
"https://api.explorium.ai/v1/prospects" \
-H "API_KEY: <your api key>" \
-H "Content-Type: application/json" \
-d '{
"mode": "full",
"size": 100,
"page_size": 100,
"page": 1,
"filters": {
"business_id": {
"values": [
"8adce3ca1cef0c986b22310e369a0793"
]
},
"job_level": {
"type": "includes",
"values": [
"director",
"manager"
]
},
"has_email": {
"type": "exists",
"value": true
},
"total_experience_months": {
"type": "range",
"gte": 3,
"lte": 6
}
}
}'
📌 Mode full
: Returns additional attributes such as job history, social links, and experience.
{
"response_context": {
"correlation_id": "d46aa78f3da148e7846fa94492f8f80a",
"request_status": "success",
"time_took_in_seconds": 1.252
},
"data": [
{
"prospect_id": "ba32fc15ccaccac027f9f9f1c3116a3333469443",
"full_name": "Brandon Kuchta",
"country_name": "united states",
"region_name": "california",
"city": "alamo",
"linkedin": "linkedin.com/in/bkuchta",
"experience": "Acd, design manager, product art direction",
"skills": "3d animation, 3d rendering, After effects, Art direction, Color correction, Color grading, Color management, Compositing, Concept design, Content marketing, Creative direction, Davinci resolve, Digital compositing, Digital marketing, Ec2, Hdr, Image compositing, Image manipulation, Interactive advertising, Interactive media, Leadership, Lighting, Live action, Look development, Matte painting, Mobile design, Modeling, Modo, Motion design, Motion graphics, Nuke, Photographic lighting, Photography, Photoshop, Post production, Pre press, Product development, Product management, Rendering, Responsive design, Retouching, Team leadership, User experience, Vfx supervision, Visual effects",
"interests": "Home improvement, Home decoration, Electronics",
"company_name": "Apple",
"company_website": "apple.com",
"company_linkedin": "linkedin.com/company/apple",
"job_department": "Marketing",
"job_seniority_level": [
"director"
],
"job_title": "Art director"
},
...
],
"total_results": 5,
"page": 1,
"total_pages": 1
}
Best Practices
Best Practices
- Use refined filters to retrieve the most relevant prospects.
- Batch requests efficiently to optimize API performance.
- Monitor pagination settings to avoid missing data.
- Ensure data freshness by running regular queries to keep prospect information up-to-date.
- Be mindful of filter coverage – some filters may return fewer results due to lower data availability, while broader filters may yield larger result sets.
Body Params - Try Me Example
mode: full
size: 100
page_size: 100,
page: 1
filters:
job_level:
type: includes
values: director, manager
has_email:
type: exists,
value: true
Note: For any unused filter, set `negate` (boolean) as empty instead of `false`, as it defaults to `false`.