> 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/release-notes/november-2026.md).

# November 2026

{% updates format="full" %}
{% update date="2026-11-01" %}

## Indeed Jobs data: adding a new field and updating an existing field value

#### Adding a new field

Adding a new field to Indeed Jobs data `date_posted` that shows the date and time the job was posted. It replaces the `date_published` field.

| Data field    | Description                                          | Data type |
| ------------- | ---------------------------------------------------- | --------- |
| `date_posted` | Date and time the job was posted in ISO 8601 format. | String    |

#### `date_published` field value update

Because the `date_published` field fill rate fluctuates, it may contain `null` values. The posting date is available in the `date_posted` field, and you should use `date_posted` field going forward.

| Data field       | Before    | After                                         |
| ---------------- | --------- | --------------------------------------------- |
| `date_published` | Populated | `null` for many records; fill rate fluctuates |
| {% endupdate %}  |           |                                               |

{% update date="2026-11-05" %}

## Multi-source Employee Data: adding new fields to Employer Information bundle

We are adding four new employer fields to the Employer Information bundle to provide richer context about the companies associated with each employee record.

{% hint style="info" %}
The following fields will be available in the Multi-source Employee API starting November 11, 2026.
{% endhint %}

| Data field                            | Description                                      | Data type       |
| ------------------------------------- | ------------------------------------------------ | --------------- |
| `experience[].company_business_areas` | Business areas in which the employer operates    | Array (strings) |
| `experience[].company_offerings`      | Products and services offered by the employer    | Array (strings) |
| `experience[].company_is_saas`        | Indicates whether the employer is a SaaS company | Boolean         |
| `experience[].company_business_model` | Business model of the employer                   | Array (strings) |
| {% endupdate %}                       |                                                  |                 |

{% update date="2026-11-11" %}

## Webhooks: subscriptions with `tracked_fields` now receive all `started_matching_query` and `stopped_matching_query` events

Previously, subscriptions with set `tracked_fields` received `started_matching_query` and `stopped_matching_query` webhooks only when a tracked field changed in the same update. Now, these events trigger a webhook whenever an employee or company profile starts or stops matching the subscription's query, regardless of `tracked_fields`. `tracked_fields` now filters only changed events, so subscriptions with configured `tracked_fields` may receive more webhook notifications than before.
{% endupdate %}

{% update date="2026-11-18" %}

## Multi-source APIs: new filter search endpoints

We are introducing filter search endpoints for Multi-source Company API and Multi-source Employee API. They let you search with named parameters instead of writing Elasticsearch DSL queries. Each parameter is named after the response field it filters, so you can build queries straight from the data schema.

| Endpoint                                                                                                                  | Description                                                                |
| ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| POST [`/v2/company_multi_source/search/filter`](https://docs.coresignal.com/company-data/api/search-filters.md)           | Search multi-source company records using named filter parameters          |
| POST [`/v2/company_multi_source/search/filter/preview`](https://docs.coresignal.com/company-data/api/search-preview.md)   | Return the preview data of company records matching the filter parameters  |
| POST [`/v2/employee_multi_source/search/filter`](https://docs.coresignal.com/employee-data/api/search-filters.md)         | Search multi-source employee records using named filter parameters         |
| POST [`/v2/employee_multi_source/search/filter/preview`](https://docs.coresignal.com/employee-data/api/search-preview.md) | Return the preview data of employee records matching the filter parameters |

Each request to a `/search/filter/preview` endpoint costs 20 credits.
{% endupdate %}

{% update date="2026-11-19" %}

## Multi-source Company data and API: adding a new field to Core bundle

We are adding the `processed_at` field to the Core bundle, the Multi-source Company dataset and API. This field records when a record was last processed and can be used to identify records that changed recently.

| Data field     | Description                                                                                                                                                | Data type |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| `processed_at` | Timestamp of the most recent processing of the record. Updated whenever the record changes, including data corrections made without a new data collection. | Timestamp |

`processed_at` works independently of `last_updated_at`. A record's `processed_at` value may therefore be more recent than its `last_updated_at` value, even when no new source data was collected.
{% endupdate %}

{% update date="2026-11-19" %}

## Multi-source Employee data: adding new fields to Core bundle

We are adding structured location fields to Core bundle for each entry in the `experience` array of the Multi-source Employee dataset. Values are derived from the entry's location, so work history can be filtered and analyzed by geography more precisely.

{% hint style="info" %}
The following fields will be available in the Multi-source Employee API starting November 25, 2026.
{% endhint %}

| Data field               | Description                          | Data type |
| ------------------------ | ------------------------------------ | --------- |
| `experience[].city`      | City of the experience location      | String    |
| `experience[].state`     | State of the experience location     | String    |
| `experience[].country`   | Country of the experience location   | String    |
| `experience[].latitude`  | Latitude of the experience location  | Float     |
| `experience[].longitude` | Longitude of the experience location | Float     |
| {% endupdate %}          |                                      |           |

{% update date="2026-11-25" %}

## Employee Posts API: adding a new field

We are adding the `processed_at` field to Employee Posts API responses. This field indicates when a record was last processed and can be used to identify recently updated posts.

| Data field       | Description                                           | Data type |
| ---------------- | ----------------------------------------------------- | --------- |
| `processed_at`   | Timestamp of the most recent processing of the record | Timestamp |
| {% endupdate %}  |                                                       |           |
| {% endupdates %} |                                                       |           |


---

# 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/release-notes/november-2026.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.
