# April 2026

## Base Jobs Data

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

## Adding new fields <a href="#base-jobs-data" id="base-jobs-data"></a>

Base Jobs data has been extended with new identification and detailed location fields, including country ISO codes, regions, city, and state.

| Data field       | Description                                                                         | Data type        |
| ---------------- | ----------------------------------------------------------------------------------- | ---------------- |
| `id`             | Identification key for a job profile record                                         | Integer          |
| `country_iso_2`  | ISO 2-letter code of the location country (based on location and/or country values) | String           |
| `country_iso_3`  | ISO 3-letter code of the location country (based on location and/or country values) | String           |
| `regions`        | Associated geographical regions based on location and/or country values             | Array of strings |
| `city`           | Job location city                                                                   | String           |
| `state`          | Job location state (if available)                                                   | String           |
| {% endupdate %}  |                                                                                     |                  |
| {% endupdates %} |                                                                                     |                  |

## Base Employee Data

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

## Removing fields <a href="#base-employee-data" id="base-employee-data"></a>

The following Base Employee fields have been removed from their respective collections due to low fill rate adding no value to the dataset.

### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

| Data field                  | Collection       |
| --------------------------- | ---------------- |
| `education.date_from_month` | Education        |
| `education.date_to_month`   | Education        |
| `others_named.deleted`      | Others Named     |
| `similar_profiles.deleted`  | Similar Profiles |
| {% endupdate %}             |                  |

{% update date="2026-04-01" %}

## Removing categories <a href="#base-employee-data" id="base-employee-data"></a>

### `hidden_details` category

The `hidden_details` category is being removed from the Base Employee schema.

Updates to the data aggregation pipeline now ensure that all necessary information is properly populated in the standard schema fields. As a result, the separate `hidden_details` identifier has become redundant.

#### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

| Data field                         | Data type        |
| ---------------------------------- | ---------------- |
| `hidden_details`                   | Array of objects |
| `hidden_details.hidden_collection` | String           |

### Legacy categories

The following legacy categories with nested fields are being removed from all future Base Employee dumps and the dataset schema, as they are no longer actively updated. However, the data is stored in our database and can be requested on demand.

#### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

<table><thead><tr><th>Removed legacy category</th><th width="254" valign="top">Impacted data fields</th></tr></thead><tbody><tr><td><code>also_viewed</code></td><td valign="top"><code>also_viewed</code> <br><code>also_viewed[].headline</code> <br><code>also_viewed[].id</code> <br><code>also_viewed[].full_name</code> <br><code>also_viewed[].profile_url</code> <br><code>also_viewed[].location</code> <br><code>also_viewed[].order_in_profile</code> <br><code>also_viewed[].deleted</code> <br><code>also_viewed[].created_at</code> <br><code>also_viewed[].updated_at</code> </td></tr><tr><td><code>groups</code></td><td valign="top"><code>groups[].title</code> <br><code>groups[].url</code> <br><code>groups[].id</code> <br><code>groups[].deleted</code> <br><code>groups[].order_in_profile</code> <br><code>groups[].created_at</code> <br><code>groups[].updated_at</code> </td></tr><tr><td><code>interests</code> </td><td valign="top"><code>interests[].interest</code> <br><code>interests[].id</code> <br><code>interests[].deleted</code> <br><code>interests[].order_in_profile</code> <code>interests[].created_at</code>  <br><code>interests[].updated_at</code> </td></tr><tr><td><code>posts_see_more_urls</code> </td><td valign="top"><code>posts_see_more_urls[].url</code> <code>posts_see_more_urls[].id</code> <code>posts_see_more_urls[].order_in_profile</code> <code>posts_see_more_urls[].deleted</code> <code>posts_see_more_urls[].created_at</code> <code>posts_see_more_urls[].updated_at</code> </td></tr><tr><td><code>skills</code></td><td valign="top"><code>skills[].skill</code> <br><code>skills[].id</code> <br><code>skills[].order_in_profile</code> <br><code>skills[].deleted</code> <br><code>skills[].created_at</code> <br><code>skills[].updated_at</code> </td></tr><tr><td><code>volunteering_cares</code> </td><td valign="top"><code>volunteering_cares[].id</code> <br><code>volunteering_cares[].care</code> <br><code>volunteering_cares[].deleted</code> <code>volunteering_cares[].order_in_profile</code> <code>volunteering_cares[].created_at</code> <code>volunteering_cares[].updated_at</code> </td></tr><tr><td><code>volunteering_opportunities</code> </td><td valign="top"><code>volunteering_opportunities[].opportunity</code> <code>volunteering_opportunities[].id</code> <code>volunteering_opportunities[].deleted</code> <code>volunteering_opportunities[].order_in_profile</code> <code>volunteering_opportunities[].created_at</code> <code>volunteering_opportunities[].updated_at</code> </td></tr><tr><td><code>volunteering_supports</code> </td><td valign="top"><code>volunteering_supports[].support</code> <br><code>volunteering_supports[].id</code> <code>volunteering_supports[].deleted</code> <code>volunteering_supports[].order_in_profile</code> <code>volunteering_supports[].created_at</code> <code>volunteering_supports[].updated_at</code></td></tr></tbody></table>

{% endupdate %}

{% update date="2026-04-01" %}

## HTML tag removal <a href="#base-employee-data" id="base-employee-data"></a>

HTML tags are being removed from the following fields incrementally:

| Data field                  |
| --------------------------- |
| `headline`                  |
| `description`               |
| `experience.description`    |
| `education.description`     |
| `awards.description`        |
| `projects.description`      |
| `organizations.description` |

{% hint style="info" %}
Newline formatting (`\n`) will be preserved. Only HTML markup will be removed.
{% endhint %}
{% endupdate %}
{% endupdates %}

## Multi-source Jobs Data

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

## Adding a new field <a href="#multi-source-jobs-data" id="multi-source-jobs-data"></a>

Added a field to mention funding round type.

| Data field                        | Description                                        | Data type |
| --------------------------------- | -------------------------------------------------- | --------- |
| `company_last_funding_round_type` | New field for funding round type (e.g. `Series A`) | String    |
| {% endupdate %}                   |                                                    |           |

{% update date="2026-04-03" %}

## Removing a data field <a href="#multi-source-jobs-data" id="multi-source-jobs-data"></a>

`company_last_funding_round_name` is removed with no direct replacement. Funding round type is now added as a separate field.

| Data field                        | Data type |
| --------------------------------- | --------- |
| `company_last_funding_round_name` | String    |
| {% endupdate %}                   |           |
| {% endupdates %}                  |           |

## Multi-source Company Data

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

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

Adding new fields for `funding_rounds` and updating schema by adding new category `last_funding_round` with nested fields.

| Data field                                                         | Description                                           | Data type        |
| ------------------------------------------------------------------ | ----------------------------------------------------- | ---------------- |
| `funding_rounds[].type`                                            | Funding round type (e.g. `Series A`)                  | String           |
| `funding_rounds[].investors`                                       | Investors information                                 | Array of structs |
| `funding_rounds[].investors[].name`                                | Investor name                                         | String           |
| `funding_rounds[].investors[].entity_id`                           | Internal entity identifier                            | Long             |
| `funding_rounds[].investors[].entity`                              | Entity type (e.g. person, organization)               | String           |
| `funding_rounds[].investors[].is_lead`                             | Indicates whether this investor led the round         | Boolean          |
| `funding_rounds[].investors[].partner_identifiers`                 | Partner-level identifiers within the investor         | Array of structs |
| `funding_rounds[].investors[].partner_identifiers[].name`          | Partner name                                          | String           |
| `funding_rounds[].investors[].partner_identifiers[].entity_id`     | Partner entity identifier                             | Long             |
| `funding_rounds[].investors[].partner_identifiers[].entity`        | Partner entity type                                   | String           |
| `funding_rounds[].num_partners`                                    | Number of partner investors in the round              | Long             |
| `last_funding_round`                                               | Last funding round information                        | Array of structs |
| `last_funding_round[].type`                                        | Funding round type (e.g. `Series A`)                  | String           |
| `last_funding_round[].announced_date`                              | Date when the funding round was announced             | Date             |
| `last_funding_round[].investors`                                   | Investors information                                 | Array of structs |
| `last_funding_round[].investors[].name`                            | Investor name                                         | String           |
| `last_funding_round[].investors[].entity_id`                       | Internal entity identifier                            | Long             |
| `last_funding_round[].investors[].entity`                          | Entity type (e.g. person, organization)               | String           |
| `last_funding_round[].investors[].is_lead`                         | Whether this investor led the round                   | Boolean          |
| `last_funding_round[].investors[].partner_identifiers`             | Partner-level identifiers within the investor         | Array of structs |
| `last_funding_round[].investors[].partner_identifiers[].name`      | Partner name                                          | String           |
| `last_funding_round[].investors[].partner_identifiers[].entity_id` | Partner entity identifier                             | Long             |
| `last_funding_round[].investors[].partner_identifiers[].entity`    | Partner entity type                                   | String           |
| `last_funding_round[].amount_raised`                               | Amount raised in the last funding round               | Long             |
| `last_funding_round[].amount_raised_currency`                      | Last funding round currency                           | String           |
| `last_funding_round[].num_investors`                               | Number of investors in the funding round              | Long             |
| `last_funding_round[].num_partners`                                | Number of partner investors in the last funding round | Long             |
| {% endupdate %}                                                    |                                                       |                  |

{% update date="2026-04-01" %}

## Removing fields <a href="#multi-source-company-data" id="multi-source-company-data"></a>

We are making schema improvements to the dataset, and some of the removed fields are changed by other nested fields.

| `funding_rounds[].name`                     | No direct replacement. Funding round type is now a separate field                         | String           |
| ------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------- |
| `funding_rounds[].lead_investors`           | `funding_rounds[].lead_investors` field is replaced by `funding_rounds[].investors` field | Array of strings |
| `last_funding_round_name`                   | Replaced by `last_funding_round` nested struct                                            | String           |
| `last_funding_round_announced_date`         | Replaced by `last_funding_round` nested struct                                            | Date             |
| `last_funding_round_lead_investors`         | Replaced by `last_funding_round` nested struct                                            | Array of structs |
| `last_funding_round_amount_raised`          | Replaced by `last_funding_round` nested struct                                            | Long             |
| `last_funding_round_amount_raised_currency` | Replaced by `last_funding_round` nested struct                                            | String           |
| `last_funding_round_num_investors`          | Replaced by `last_funding_round` nested struct                                            | Long             |
| {% endupdate %}                             |                                                                                           |                  |
| {% endupdates %}                            |                                                                                           |                  |

## Logic changes

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

## Job title classification updates

### Changes

We are improving our job title classification system with refined department and management level categories.

### Impacted fields

| Dataset                    | Data fields                                                                                                                                                                                                                                                                                                                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Multi-source Company data  | <ul><li><code>key\_executives</code></li><li><code>key\_executive\_arrivals</code></li><li><code>key\_executive\_departures</code></li><li><code>employees\_count\_breakdown\_by\_seniority</code></li><li><code>employees\_count\_breakdown\_by\_department</code></li><li><code>employees\_count\_breakdown\_by\_seniority\_by\_month</code></li><li><code>employees\_count\_breakdown\_by\_department\_by\_month</code></li></ul>  |
| Multi-source Employee data | <ul><li><code>active\_experience\_department</code></li><li><code>active\_experience\_management\_level</code></li><li><code>is\_decision\_maker</code></li><li><code>experience.department</code></li><li><code>experience.management\_level</code></li><li><code>total\_experience\_duration\_months\_breakdown\_management\_level</code></li><li><code>total\_experience\_duration\_months\_breakdown\_department</code></li></ul> |
| Multi-source Jobs data     | <ul><li><code>department</code></li><li><code>management\_level</code></li><li><code>is\_decision\_maker</code></li></ul>                                                                                                                                                                                                                                                                                                             |
| Clean Employee data        | <ul><li><code>department</code></li><li><code>management\_level</code></li></ul>                                                                                                                                                                                                                                                                                                                                                      |

#### C-Level migration: `department` → `management_level`

* The `"C-Suite"` department has been eliminated (previously 2.3M records).
* C-Level executives are now classified by their functional department (e.g., CFO → `Finance & Accounting`, CTO → `Engineering and Technical`), with `"C-Level"` assigned as their management level.

#### Reduced "Other" classifications

* The "Other" department has dropped from 8.9M to 2.1M records (76% reduction) as significantly more job titles are now accurately categorized into specific departments.

#### New category: "General Management"

* A new "General Management" department has been added to capture leadership roles that span multiple functions (4.5M records).

***

### Supported values

#### Departments

`Administrative` · `Consulting` · `Customer Service` · `Design` · `Education` · `Engineering and Technical` · `Finance & Accounting` · `General Management` · `Human Resources` · `Legal` · `Marketing` · `Medical` · `Operations` · `Other` · `Product` · `Project Management` · `Real Estate` · `Research` · `Sales` · `Trades`

#### Management levels

`C-Level` · `Director` · `Founder` · `Head` · `Intern` · `Manager` · `Owner` · `Partner` · `President/Vice President` · `Senior` · `Specialist`

***

### Classification examples

| Title                    | Department                | Management level         |
| ------------------------ | ------------------------- | ------------------------ |
| CEO                      | General Management        | C-Level                  |
| CFO                      | Finance & Accounting      | C-Level                  |
| CTO                      | Engineering and Technical | C-Level                  |
| Director of Engineering  | Engineering and Technical | Director                 |
| VP of Sales              | Sales                     | President/Vice President |
| Marketing Manager        | Marketing                 | Manager                  |
| Senior Software Engineer | Engineering and Technical | Senior                   |
| Software Engineer        | Engineering and Technical | Specialist               |
| {% endupdate %}          |                           |                          |
| {% endupdates %}         |                           |                          |

## Experience and Education Update

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

## Overview

We are releasing an update to the Experience and Education categories in employee data. This release includes schema additions, data quality improvements, and a change to the ordering of active experiences. To apply all changes smoothly, the delivery for this update will be a full reload of both collections.

### Added new fields

Adding new data fields to experience categories.

#### Clean Employee Data

| Data field                                   | Description                                   | Data type |
| -------------------------------------------- | --------------------------------------------- | --------- |
| `member_experience[].company_shorthand_name` | Shorthand / vanity identifier for the company | String    |
| `member_experience[].company_website`        | Company website URL                           | String    |

#### Multi-source Employee Data

| Data field                                              | Description                                                | Data type |
| ------------------------------------------------------- | ---------------------------------------------------------- | --------- |
| `experience[].active_experience_company_website`        | Website of the company in the employee's active experience | String    |
| `experience[].active_experience_company_shorthand_name` | Shorthand name of the company in the active experience     | String    |
| `experience[].active_experience_company_logo_url`       | Logo URL of the company in the active experience           | String    |

### Data improvements

#### 1. Data quality improvements <a href="#id-1.-data-quality-improvements" id="id-1.-data-quality-improvements"></a>

* **Stale deleted records removed**

Previous mapping logic could classify an experience as active (`deleted: 0`) even after the record stopped being updated. These records have now been identified and corrected. As a result, you may see a net reduction in `deleted: 0` experience counts. This change reflects cleaner, more accurate data, not data loss.

* **Improved fill rate on key fields**

The updated mapping logic improves coverage on two critical experience fields:

| Data field  | Improvement                            |
| ----------- | -------------------------------------- |
| `title`     | Higher fill rate and fewer null values |
| `date_from` | Higher fill rate and fewer null values |

#### 2. Change in `active_experience` ordering <a href="#id-2.-change-in-active_experience-ordering" id="id-2.-change-in-active_experience-ordering"></a>

The first entry in the `active_experience` array will now be ordered by greatest `date_from` (i.e. most recent active experience first).

Previously, ordering was based on `order_in_profile`, which could produce inconsistent results due to the legacy mapping logic. The new ordering is deterministic and reflects the employee's most recent active role.

{% hint style="info" %}

#### **Action required if you consume `active_experience[0]`**

Verify that your pipeline handles the new ordering correctly. The most recent experience will now always appear first.
{% endhint %}
{% endupdate %}
{% endupdates %}

## Base Employee API

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

## Removing fields <a href="#base-employee-api" id="base-employee-api"></a>

The following Base Employee API fields have been removed from their respective collections due to low fill rate adding no value to the dataset.

### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

| Data field                  | Collection       |
| --------------------------- | ---------------- |
| `education.date_from_month` | Education        |
| `education.date_to_month`   | Education        |
| `others_named.deleted`      | Others Named     |
| `similar_profiles.deleted`  | Similar Profiles |
| {% endupdate %}             |                  |

{% update date="2026-04-01" %}

## Removing categories <a href="#base-employee-api" id="base-employee-api"></a>

### `hidden_details` category

The `hidden_details` category is being removed from the Base Employee API.

Updates to the data aggregation pipeline now ensure that all necessary information is properly populated in the standard schema fields. As a result, the separate `hidden_details` identifier has become redundant.

#### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

| Data field                         | Data type        |
| ---------------------------------- | ---------------- |
| `hidden_details`                   | Array of objects |
| `hidden_details.hidden_collection` | String           |

### Legacy categories

The following legacy categories with nested fields are being removed from Base Employee API as they are no longer actively updated.

#### &#x20;<mark style="color:$danger;">**Removed fields**</mark>

<table><thead><tr><th>Removed legacy category</th><th width="254" valign="top">Impacted data fields</th></tr></thead><tbody><tr><td><code>also_viewed</code></td><td valign="top"><code>also_viewed</code> <br><code>also_viewed[].headline</code> <br><code>also_viewed[].id</code> <br><code>also_viewed[].full_name</code> <br><code>also_viewed[].profile_url</code> <br><code>also_viewed[].location</code> <br><code>also_viewed[].order_in_profile</code> <br><code>also_viewed[].deleted</code> <br><code>also_viewed[].created_at</code> <br><code>also_viewed[].updated_at</code> </td></tr><tr><td><code>groups</code></td><td valign="top"><code>groups[].title</code> <br><code>groups[].url</code> <br><code>groups[].id</code> <br><code>groups[].deleted</code> <br><code>groups[].order_in_profile</code> <br><code>groups[].created_at</code> <br><code>groups[].updated_at</code> </td></tr><tr><td><code>interests</code> </td><td valign="top"><code>interests[].interest</code> <br><code>interests[].id</code> <br><code>interests[].deleted</code> <br><code>interests[].order_in_profile</code> <code>interests[].created_at</code>  <br><code>interests[].updated_at</code> </td></tr><tr><td><code>posts_see_more_urls</code> </td><td valign="top"><code>posts_see_more_urls[].url</code> <code>posts_see_more_urls[].id</code> <code>posts_see_more_urls[].order_in_profile</code> <code>posts_see_more_urls[].deleted</code> <code>posts_see_more_urls[].created_at</code> <code>posts_see_more_urls[].updated_at</code> </td></tr><tr><td><code>skills</code></td><td valign="top"><code>skills[].skill</code> <br><code>skills[].id</code> <br><code>skills[].order_in_profile</code> <br><code>skills[].deleted</code> <br><code>skills[].created_at</code> <br><code>skills[].updated_at</code> </td></tr><tr><td><code>volunteering_cares</code> </td><td valign="top"><code>volunteering_cares[].id</code> <br><code>volunteering_cares[].care</code> <br><code>volunteering_cares[].deleted</code> <code>volunteering_cares[].order_in_profile</code> <code>volunteering_cares[].created_at</code> <code>volunteering_cares[].updated_at</code> </td></tr><tr><td><code>volunteering_opportunities</code> </td><td valign="top"><code>volunteering_opportunities[].opportunity</code> <code>volunteering_opportunities[].id</code> <code>volunteering_opportunities[].deleted</code> <code>volunteering_opportunities[].order_in_profile</code> <code>volunteering_opportunities[].created_at</code> <code>volunteering_opportunities[].updated_at</code> </td></tr><tr><td><code>volunteering_supports</code> </td><td valign="top"><code>volunteering_supports[].support</code> <br><code>volunteering_supports[].id</code> <code>volunteering_supports[].deleted</code> <code>volunteering_supports[].order_in_profile</code> <code>volunteering_supports[].created_at</code> <code>volunteering_supports[].updated_at</code></td></tr></tbody></table>
{% endupdate %}

{% update date="2026-04-01" %}

## Replacing `"skill"` Search filter <a href="#base-employee-api" id="base-employee-api"></a>

This release introduces a breaking change to Employee Base API Search filters. Search filter `"skill"` was replaced with `"inferred_skills"` due to corresponding schema updates.

| Change                                                    | Details                                                         |
| --------------------------------------------------------- | --------------------------------------------------------------- |
| <mark style="color:$danger;">Removed Search filter</mark> | Removed `skills` from the Employee Base API Search filters list |
| <mark style="color:$success;">Added Search filter</mark>  | Added `inferred_skills` under Employee Base API Search filters. |
| {% endupdate %}                                           |                                                                 |

{% update date="2026-04-01" %}

## Removing `"is_hidden"` Search filter <a href="#base-employee-api" id="base-employee-api"></a>

Search filter `"is_hidden"` was removed due to corresponding schema updates.

| Change                                                    | Details                                                            |
| --------------------------------------------------------- | ------------------------------------------------------------------ |
| <mark style="color:$danger;">Removed Search filter</mark> | Removed `is_hidden` from the Employee Base API Search filters list |
| {% endupdate %}                                           |                                                                    |
| {% endupdates %}                                          |                                                                    |

## Multi-source Company API

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

## Adding new fields <a href="#multi-source-company-api" id="multi-source-company-api"></a>

Adding new fields for `funding_rounds` and updating schema by adding new category `last_funding_round` with nested fields.

| Data field                                                         | Description                                           | Data type        |
| ------------------------------------------------------------------ | ----------------------------------------------------- | ---------------- |
| `funding_rounds[].type`                                            | Funding round type (e.g. `Series A`)                  | String           |
| `funding_rounds[].investors`                                       | Investors information                                 | Array of structs |
| `funding_rounds[].investors[].name`                                | Investor name                                         | String           |
| `funding_rounds[].investors[].entity_id`                           | Internal entity identifier                            | Long             |
| `funding_rounds[].investors[].entity`                              | Entity type (e.g. person, organization)               | String           |
| `funding_rounds[].investors[].is_lead`                             | Indicates whether this investor led the round         | Boolean          |
| `funding_rounds[].investors[].partner_identifiers`                 | Partner-level identifiers within the investor         | Array of structs |
| `funding_rounds[].investors[].partner_identifiers[].name`          | Partner name                                          | String           |
| `funding_rounds[].investors[].partner_identifiers[].entity_id`     | Partner entity identifier                             | Long             |
| `funding_rounds[].investors[].partner_identifiers[].entity`        | Partner entity type                                   | String           |
| `funding_rounds[].num_partners`                                    | Number of partner investors in the round              | Long             |
| `last_funding_round`                                               | Last funding round information                        | Array of structs |
| `last_funding_round[].type`                                        | Funding round type (e.g. `Series A`)                  | String           |
| `last_funding_round[].announced_date`                              | Date when the funding round was announced             | Date             |
| `last_funding_round[].investors`                                   | Investors information                                 | Array of structs |
| `last_funding_round[].investors[].name`                            | Investor name                                         | String           |
| `last_funding_round[].investors[].entity_id`                       | Internal entity identifier                            | Long             |
| `last_funding_round[].investors[].entity`                          | Entity type (e.g. person, organization)               | String           |
| `last_funding_round[].investors[].is_lead`                         | Whether this investor led the round                   | Boolean          |
| `last_funding_round[].investors[].partner_identifiers`             | Partner-level identifiers within the investor         | Array of structs |
| `last_funding_round[].investors[].partner_identifiers[].name`      | Partner name                                          | String           |
| `last_funding_round[].investors[].partner_identifiers[].entity_id` | Partner entity identifier                             | Long             |
| `last_funding_round[].investors[].partner_identifiers[].entity`    | Partner entity type                                   | String           |
| `last_funding_round[].amount_raised`                               | Amount raised in the last funding round               | Long             |
| `last_funding_round[].amount_raised_currency`                      | Last funding round currency                           | String           |
| `last_funding_round[].num_investors`                               | Number of investors in the funding round              | Long             |
| `last_funding_round[].num_partners`                                | Number of partner investors in the last funding round | Long             |
| {% endupdate %}                                                    |                                                       |                  |

{% update date="2026-04-08" %}

## Removing fields <a href="#multi-source-company-api" id="multi-source-company-api"></a>

We are making schema improvements to the dataset, and some of the removed fields are changed by other nested fields.

| `funding_rounds[].name`                     | No direct replacement. Funding round type is now a separate field                         | String           |
| ------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------- |
| `funding_rounds[].lead_investors`           | `funding_rounds[].lead_investors` field is replaced by `funding_rounds[].investors` field | Array of strings |
| `last_funding_round_name`                   | Replaced by `last_funding_round` nested struct                                            | String           |
| `last_funding_round_announced_date`         | Replaced by `last_funding_round` nested struct                                            | Date             |
| `last_funding_round_lead_investors`         | Replaced by `last_funding_round` nested struct                                            | Array of structs |
| `last_funding_round_amount_raised`          | Replaced by `last_funding_round` nested struct                                            | Long             |
| `last_funding_round_amount_raised_currency` | Replaced by `last_funding_round` nested struct                                            | String           |
| `last_funding_round_num_investors`          | Replaced by `last_funding_round` nested struct                                            | Long             |
| {% endupdate %}                             |                                                                                           |                  |
| {% endupdates %}                            |                                                                                           |                  |

## Multi-source Employee API

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

## Adding new fields <a href="#multi-source-employee-api" id="multi-source-employee-api"></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 %}                                |                                                      |           |

## Multi-source Jobs API

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

## Adding a new field <a href="#multi-source-jobs-api" id="multi-source-jobs-api"></a>

Added a field to mention funding round type.

| Data field                        | Description                                        | Data type |
| --------------------------------- | -------------------------------------------------- | --------- |
| `company_last_funding_round_type` | New field for funding round type (e.g. `Series A`) | String    |
| {% endupdate %}                   |                                                    |           |

{% update date="2026-04-08" %}

## Removing a data field <a href="#multi-source-jobs-api" id="multi-source-jobs-api"></a>

`company_last_funding_round_name` is removed with no direct replacement. Funding round type is now added as a separate field.

| Data field                        | Data type |
| --------------------------------- | --------- |
| `company_last_funding_round_name` | String    |
| {% endupdate %}                   |           |
| {% endupdates %}                  |           |