Using the Employees Endpoint
Endpoint:GET /contractors/{id}/employees
Required Parameters
{id}- The contractor ID (path parameter)
Optional Parameters
cursor- For pagination through large result setspage- Page number for offset-based paginationsize- Number of items per page (1-100)
Sample Request
Response Data
Contact Information
email- Personal email addressbusiness_email- Business email addressphone- Phone numberlinkedin_url- LinkedIn profile
Professional Details
job_title- Current positionseniority_level- Senior, Mid, Junior, etc.department- Department or division
Additional Data
name- Full name- Address details (street, city, state, zip)
- Demographics (age range, income range, etc.)
Scaling Your Data Collection
Pagination
Use cursor-based pagination for large employee lists. Check fornext_cursor in the response to retrieve subsequent pages.
Bulk Processing
To process multiple contractors at scale:- Obtain contractor IDs using the contractors search endpoints
- Iterate through each contractor ID
- Call the employees endpoint for each contractor
- Implement proper error handling and rate limiting
Targeting Decision Makers
Filter results byseniority_level (Senior, Executive) and job_title to identify:
- Owners
- Sales directors
- Project managers
- Other key personnel
Best Practices
- Respect rate limits and avoid frivolous requests
- Use pagination to handle large datasets efficiently
- Store and cache results to minimize API calls
- Filter by job titles and seniority levels to focus on decision-makers
- Always include proper error handling in your implementation
