> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/additional-sources/professional-network-data/base-jobs-api.md).

# Base Jobs API

Search and collect continuously updated global job postings using search filters or Elasticsearch DSL, with Bulk Collect support.

Base Jobs API provides programmatic access to a continuously updated, global dataset of job postings scraped since August 2020 – giving you both real-time hiring signals and over five years of historical data to work with.

## Overview

This section covers general details about Base Jobs API. Follow the links inside the topics to find out more details on the API and its endpoints.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Base Jobs API endpoints</td><td><a href="/additional-sources/professional-network-data/base-jobs-api.md#base-jobs-api-endpoints">Base Jobs API</a></td></tr><tr><td>Rate limits</td><td><a href="/api-introduction/rate-limits.md">Rate Limits</a></td></tr><tr><td>Credits</td><td><a href="/api-introduction/credits.md">Credits</a></td></tr></tbody></table>

## Base Jobs API endpoints

Use the endpoints with any API-compatible application to retrieve job posting data – sourced from global markets, discovered 24/7, and with every active posting revisited within 24 hours to keep status signals accurate.

{% hint style="info" %}
Our API is a data retrieval tool. The endpoints do not support analytic features.
{% endhint %}

Base Jobs API features **four search** and **one collect** endpoint.

{% hint style="warning" %}
All Jobs data API requests must be made over HTTPS. Requests made over HTTP will fail or be redirected to HTTPS.
{% endhint %}

Jobs data API supports two types of requests:

* **Search** endpoints support POST requests only.
* **Collect** endpoints support the GET requests only.

<table><thead><tr><th width="300.47265625">Endpoint</th><th width="299.6484375">Function</th><th>Credits</th></tr></thead><tbody><tr><td>POST <a href="/additional-sources/professional-network-data/base-jobs-api/search-filters.md"><em>/v2/job_base/search/filter</em></a></td><td>Search for relevant job postings using search filters</td><td>Free</td></tr><tr><td>POST <a href="/additional-sources/professional-network-data/base-jobs-api/search-preview.md"><em>/v2/job_base/search/filter/preview</em></a></td><td>Retrieves a small set of partial data using Search Filter queries</td><td>10</td></tr><tr><td>POST <a href="/additional-sources/professional-network-data/base-jobs-api/elasticsearch-dsl.md"><em>/v2/job_base/search/es_dsl</em></a></td><td>Search for relevant job postings using Elasticsearch DSL schema</td><td>Free</td></tr><tr><td>POST <a href="/additional-sources/professional-network-data/base-jobs-api/search-preview.md"><em>/v2/job_base/search/es_dsl/preview</em></a></td><td>Retrieves a small set of partial data using Elasticsearch DSL queries</td><td>10</td></tr><tr><td>GET <a href="/additional-sources/professional-network-data/base-jobs-api/collect.md"><em>/v2/job_base/collect/{job_id}</em></a></td><td>Collect job posting data using IDs</td><td>1</td></tr></tbody></table>

### Bulk Collect

Bulk Collect (Bulk API) expands Base Jobs API's functionality and features **two POST** and **two GET** endpoints.

| Request type | Endpoint URL and function                                                                                                                                 |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| POST         | [*/v2/data\_requests/job\_base/id\_file*](/additional-sources/professional-network-data/base-jobs-api/bulk-collect/post-requests.md#id-file-requests)     |
| POST         | [*/v2/data\_requests/job\_base/filter*](/additional-sources/professional-network-data/base-jobs-api/bulk-collect/post-requests.md#search-filter-requests) |
| GET          | */v2/data\_requests/{data\_request\_id}/files*                                                                                                            |
| GET          | */v2/data\_requests/{data\_request\_id}/files/{file\_name}*                                                                                               |

Read more about Bulk Collect in the following article:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Bulk Collect</td><td><a href="/api-introduction/requests/bulk-collect.md">Bulk Collect</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/additional-sources/professional-network-data/base-jobs-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.