Jobs Data API
Our API is a data retrieval tool. The endpoints do not support analytic features.
Jobs data API features two search and one collect endpoints. Use the endpoints with any API-compatible application to retrieve Professional Network Job posting data.
Endpoint and function |
|---|
/v1/professional_network/job/search/filter [Search] |
/v1/professional_network/job/search/es_dsl [Search] |
/v1/professional_network/job/collect/{job_id} [Collect] |
All Jobs data API requests must be made over HTTPS. Requests made over HTTP will fail.
Jobs data API supports two types of requests:
- Search endpoints support POST HTTP requests only.
- Collect endpoints support the GET HTTP requests only.
Request type | Endpoint | Function |
|---|---|---|
POST | Search for relevant job postings using search filters | |
POST | Search for relevant job postings using Elasticsearch DSL schema | |
GET | Collect Job posting data using IDs |
Jobs data API endpoints restrict the number of requests allowed per second for each client's API token.
Jobs data API search endpoints
Jobs data API collection endpoints
Bulk Collect POST endpoints
Bulk Collect GET endpoints
Allow 18 requests per second.
Allow 54 requests per second.
Allow 27 requests per second.
Allow 27 requests per second.
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. You can also get the token from Coresignal's self-service platform.
All requests to the Jobs data API must contain an Authorization header that consists of a Bearer authentication string and the JSON Web Token (JWT).
Use any API-compatible tool to authorize and start querying in the API. If you're unsure where to begin, check out the Postman authorization tutorial:
The token issued for you has a set amount of search and collect credits.
One search credit is deducted for one successful (200) request in the search endpoints:
- /v1/professional_network/job/search/filter
- /v1/professional_network/job/search/es_dsl
One collect credit is deducted for one successful (200) request in the collection endpoint /v1/professional_network/job/collect/{job_id}.
Remember that making one Bulk Collect request will consume more credits as you get bigger data batches.
Discuss your credit needs with your account manager.
Every search and collect response contains an X-Credits-Remaining header that shows the number of credits left in your account.
You can find the credit balance by clicking Headers in Postman.
Example of remaining credits header:
Explore what data points we offer in our API jobs data: