post https://api.explorium.ai/v1/prospects
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
).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 |
PMode 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
Parameter | Description |
---|---|
has_email | Filters only prospects that have an email. |
has_phone_number | Filters only prospects that have a phone number. |
job_level | Filters by job level. Options: director , manager , vp , partner , cxo , non-managerial , senior , entry , training , unpaid . |
job_department | Filters by job department. Options: customer service , design , education , engineering , finance , general , health , human resources , legal , marketing , media , operations , public relations , real estate , sales , trades , unknown . |
business_id | Filters prospects from specified businesses. |
total_experience_months | Selects a range of experience months (range filter). |
current_role_months | Filters by experience in the current role (range filter). |
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`.