Bulk Collect
Discover the Bulk API (Bulk Collect) capabilities and explore potential uses for efficiently retrieving employee data in bulk.
Bulk API (Bulk Collect) is an extension of Employee API and includes three POST and two GET endpoints.
Collect employee data in bulk using an ID list, search filters, or Elasticsearch DSL schema that is already used in the Employee API.
Function | Endpoint |
---|---|
POST | /v1/professional_network/employee/bulk_collect/id_file |
POST | /v1/professional_network/employee/bulk_collect/filter |
POST | /v1/professional_network/employee/bulk_collect/es_dsl |
GET | /v1/bulk_collect/{data_request_id}/files |
GET | /v1/bulk_collect/{data_request_id}/files/{file_name} |
Use the same token you have received for your Employee API usage. Your credits for Employee API will also apply to Bulk Collect data collection requests.
The credits are deducted after making the POST request.
The number of credits deducted from your account depends on the data records you download. For instance, collecting 100 profiles will consume 100 credits.
Test POST requests using Employee API to see how many credits the request will consume.
The returned record count will show how many credits will be deducted for the Bulk Collect query.
Include the parameter "limit": int to control the number of records returned by your queries in /v1/professional_network/employee/bulk_collect/filter and /v1/professional_network/employee/bulk_collect/es_dsl endpoints. This parameter is entirely optional; however, use it to make sure you don't use too many credits with your Bulk Collect queries.
Input the exact number of records you want to be returned or delete the parameter if you don't need a set limit for your request.
To start using our API, you need a (JWT) token. Your account manager or sales will generate the token for you upon your request for the API plan.
All Bulk Collect requests must contain an Authorization header consisting of a Bearer authentication string and the JSON Web Token (JWT).
All Employee API requests must be made over HTTPS. Requests made over HTTP will fail.
Use any API-compatible tool to authorize and start using the API. If you're unsure where to begin, check out the cURL authorization tutorial:
Bulk Collect endpoints have limited requests allowed per client's API token per second.
Function | Endpoint | Rate limit |
---|---|---|
POST | /v1/professional_network/employee/bulk_collect/id_file | 27 requests per second |
POST | /v1/professional_network/employee/bulk_collect/filter | 27 requests per second |
POST | /v1/professional_network/employee/bulk_collect/es_dsl | 27 requests per second |
GET | /v1/bulk_collect/{data_request_id}/files | 27 requests per second |
GET | /v1/bulk_collect/{data_request_id}/files/{file_name} | 27 requests per second |
POST endpoints allow you to add webhooks and get notified when your data request is ready.
Check the endpoint usage tutorials in the following articles:
Find examples and instructions for the Bulk Collect POST requests.
Find examples and instructions for the Bulk Collect GET requests.