> 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/search-preview.md). # Search Preview: Base Jobs API {% columns %} {% column width="16.666666666666664%" %} Data type: Query type: URLs: {% endcolumn %} {% column %} Base Jobs Coresignal's custom filters and Elasticsearch DSL {% endcolumn %} {% endcolumns %} *** ## Overview Retrieve a limited set of fields from top-matching records in real time, and search suggestion features. The preview queries the same deduplicated, globally sourced dataset as the full search endpoints – records with active postings revisited within 24 hours, so preview results reflect the same freshness and historical depth you will get at full scale. Here, Base Jobs API search `/v2/job_base/search/filter/preview` and `/v2/job_base/search/es_dsl/preview` endpoints' usage is reviewed.
General information about search previewBroken link
## Request queries See the request examples of `preview` endpoints. Search Preview endpoints accept the same query structure as their corresponding Search endpoints. {% tabs %} {% tab title="Search Filter request" %} {% code title="Search Filter request" %} ```json curl -X 'POST' \ 'https://api.coresignal.com/cdapi/v2/job_base/search/filter/preview' \ -H 'accept: application/json' \ -H 'apikey: {API Key}' \ -H 'Content-Type: application/json' \ -d '{ "created_at_gte": "2025-08-01 00:00:00", "title": "Data Analyst", "employment_type": "Full-time" }' ``` {% endcode %} {% endtab %} {% tab title="Elasticsearch DSL request" %} {% code title="Elasticsearch DSL request" %} ```json curl -X 'POST' \ 'https://api.coresignal.com/cdapi/v2/job_base/search/es_dsl/preview' \ -H 'accept: application/json' \ -H 'apikey: {API Key}' \ -H 'Content-Type: application/json' \ -d '{ "query": { "match": { "title": { "query": "Project manager", "operator": "and" } } } }' ``` {% endcode %} {% endtab %} {% endtabs %} ## Response structure Here is an overview of the fields that are retrieved using the Base Jobs API search preview endpoints. | Data field | Description | Data type | | -------------- | -------------------------------------------------- | --------- | | `id` | Identification key for a job posting record | Integer | | `created` | The time and date when we first scraped the record | String | | `title` | Job title | String | | `location` | Job location | String | | `company_name` | Company name | String | | `_score` | Elasticsearch score | Float | **Refer to the data example here:** {% hint style="info" %} All personal/company information mentioned within this context is entirely fictional and is solely intended for illustrative purposes. {% endhint %} {% tabs %} {% tab title="Search Filter response" %} {% code title="Search Filter response" %} ```json { "id": 123456789, "created": "2025-09-01 00:00:00", "title": "Data Analyst", "location": "New York, NY", "company_name": "Example Company", "_score": 10.1233456 } ``` {% endcode %} {% endtab %} {% tab title="Elasticsearch DSL response" %} {% code title="Elasticsearch DSL response" %} ```json { "id": 123456789, "created": "2025-09-01 00:00:00", "title": "Data Analyst", "location": "New York, NY", "company_name": "Example Company", "_score": 10.1233456 } ``` {% endcode %} {% endtab %} {% endtabs %} ## Pagination Examples of the request using pagination query parameter `page`. {% tabs %} {% tab title="Search Filter request" %} {% code title="Search Filter request" %} ```json curl -X 'POST' \ 'https://api.coresignal.com/cdapi/v2/job_base/search/filter/preview?page=3' \ -H 'accept: application/json' \ -H 'apikey: {API Key}' \ -H 'Content-Type: application/json' \ -d '{ "created_at_gte": "2025-08-01 00:00:00", "title": "Data Analyst", "employment_type": "Full-time" }' ``` {% endcode %} {% endtab %} {% tab title="Elasticsearch DSL request" %} {% code title="Elasticsearch DSL request" %} ```json curl -X 'POST' \ 'https://api.coresignal.com/cdapi/v2/job_base/search/es_dsl/preview?page=5' \ -H 'accept: application/json' \ -H 'apikey: {API Key}' \ -H 'Content-Type: application/json' \ -d '{ "query": { "match": { "title": { "query": "Project manager", "operator": "and" } } } }' ``` {% endcode %} {% endtab %} {% endtabs %} --- # 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/search-preview.md?ask=&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.