# February 2026

## Multi-source Employee Data

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

## Adding new fields <a href="#multi-source-employee-data" id="multi-source-employee-data"></a>

Adding three new fields to improve tracking of canonical shorthand names, awards, and certifications.

| Data field                                      | Description                                          | Data type |
| ----------------------------------------------- | ---------------------------------------------------- | --------- |
| `professional_network_canonical_shorthand_name` | The most recent version of employee’s shorthand name | String    |
| `awards_count`                                  | Count of user awards                                 | String    |
| `certifications_count`                          | Count of user certifications                         | String    |
| {% endupdate %}                                 |                                                      |           |
| {% endupdates %}                                |                                                      |           |

## Clean Company Data

{% updates format="full" %}
{% update date="2026-02-25" %}

## Adding and fixing fields <a href="#clean-company-data" id="clean-company-data"></a>

#### Added fields

We are adding new company HQ location fields.&#x20;

| Data field                          | Description                                       | Data type |
| ----------------------------------- | ------------------------------------------------- | --------- |
| `company_location_hq_country_iso_2` | ISO 2-letter country code for company HQ location | String    |
| `company_location_hq_country_iso_3` | ISO 3-letter country code for company HQ location | String    |
| `company_location_hq_state`         | Company HQ state                                  | String    |
| `company_location_hq_city`          | Company HQ city                                   | String    |

#### Fixed fields

We are fixing inaccuracies in Clean Company schema, specifically  `company_locations_full` nested fields, that were referenced in the December 2025 schema update but were not fully launched. The issue has now been resolved, and the previously missing fields are available in the Clean Company schema.

| Data field                             | Description                           | Data type        |
| -------------------------------------- | ------------------------------------- | ---------------- |
| `company_locations_full.country`       | Fixed country name field              | String           |
| `company_locations_full.country_iso_2` | Fixed ISO 2-letter country field      | String           |
| `company_locations_full.country_iso_3` | Fixed ISO 3-letter country code field | String           |
| `company_locations_full.regions`       | Fixed regions array field             | Array of structs |
| `company_locations_full.state`         | Fixed state field                     | String           |
| `company_locations_full.city`          | Fixed city field                      | String           |
| {% endupdate %}                        |                                       |                  |
| {% endupdates %}                       |                                       |                  |

## Employee Posts API

{% updates format="full" %}
{% update date="2026-02-04" %}

## Adding new fields <a href="#employee-posts-api" id="employee-posts-api"></a>

Adding two fields to improve data mapping experience

| Data field                         | Description                         | Data type |
| ---------------------------------- | ----------------------------------- | --------- |
| `employee_parent_id`               | Employee profile identification key | String    |
| `reshared_post.employee_parent_id` | Author profile identification key   | String    |
| {% endupdate %}                    |                                     |           |
| {% endupdates %}                   |                                     |           |

## Webhooks

{% updates format="full" %}
{% update date="2026-02-09" %}

## Experience webhooks update <a href="#webhooks" id="webhooks"></a>

Promotions (for example, a new position at a company where the individual previously worked) now trigger a webhook event. Webhooks will be sent for internal role changes, enabling better tracking of promotions and career progression.
{% endupdate %}
{% endupdates %}

## Real-time Employee API

{% updates format="full" %}
{% update date="2026-02-09" %}

## Supporting a new endpoint <a href="#real-time-employee-api" id="real-time-employee-api"></a>

Supporting a new endpoint to retrieve real-time Base Employee data. The Real-time Employee API enables faster, more efficient data retrieval.

### &#x20;<mark style="color:$success;">Added endpoint</mark>

| Request type | Endpoint                                                |
| ------------ | ------------------------------------------------------- |
| POST         | *<https://api.coresignal.com/rtapi/v2/employee/scrape>* |

Find all the information in [Real-time Employee API](https://app.gitbook.com/s/cyJAXlZjTKSLvAQjb9rM/employee-api/real-time-employee-api) topic.
{% endupdate %}
{% endupdates %}

## Base Employee API

{% updates format="full" %}
{% update date="2026-02-25" %}

## Deprecating an endpoint <a href="#base-employee-api" id="base-employee-api"></a>

The `/v2/employee_base/map/ids` endpoint is deprecated due to low usage and limited need for IDs mapping between Base Employee and Legacy Employee APIs.
{% endupdate %}

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

## Elasticsearch DSL schema update <a href="#base-employee-api" id="base-employee-api"></a>

The field structure of selected fields was modified, enabling exact matching in Elasticsearch DSL queries.

These structural changes allow users to run exact-match queries on the listed fields, adding more flexibility for building queries and enabling lighter queries with fewer multi-level batches.

#### Updated fields

The following fields were updated to support exact match search:

* `experience.title`
* `full_name`
* `first_name`
* `last_name`
* `experience.location`
* `skills.skill`
* `certifications.title`
* `certifications.issuer`
  {% endupdate %}
  {% endupdates %}