> 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/july-2026.md).

# July 2026

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

## Base Company data: adding new fields

We are adding new fields to expand company headquarters information.

| Data field                        | Description                                   | Data type |
| --------------------------------- | --------------------------------------------- | --------- |
| `headquarters_location.city`      | City of the company headquarters              | String    |
| `headquarters_location.street`    | Street address of the company headquarters    | String    |
| `headquarters_location.apartment` | Apartment number of the company headquarters  | String    |
| `headquarters_location.suite`     | Suite of the company headquarters             | String    |
| `headquarters_location.zip_code`  | ZIP / postal code of the company headquarters | String    |
| {% endupdate %}                   |                                               |           |

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

## Clean Company data: data fields changes

Clean Company data is migrating to use the updated Base Company data structure as its source. As part of this transition, two fields will no longer contain data and will be removed across upcoming August dump.

| Data field         | July dump                                                                                                         | August dump                                                                                                |
| ------------------ | ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| `company_ticker`   | No longer populated. The field remains present in the schema but will consistently return `null` or empty values. | Field removed from the schema. **Breaking:** Remove all dependencies on this field before the August dump. |
| `company_exchange` | No longer populated. The field remains present in the schema but will consistently return `null` or empty values. | Field removed from the schema. **Breaking:** Remove all dependencies on this field before the August dump. |
| {% endupdate %}    |                                                                                                                   |                                                                                                            |

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

## Multi-source Company data: adding new fields

Adding new fields to improve the granularity of HQ address data and to expose a full structured list of all company locations.

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>hq_latitude</code></td><td>Geographic latitude coordinate of the company's headquarters</td><td>Double</td></tr><tr><td><code>hq_longitude</code></td><td>Geographic longitude coordinate of the company's headquarters</td><td>Double</td></tr><tr><td><code>hq_apartment</code></td><td>Apartment number or unit identifier for the HQ address, when applicable</td><td>String</td></tr><tr><td><code>hq_suite</code></td><td>Suite number or office designator for the HQ address, when applicable</td><td>String</td></tr><tr><td><code>company_locations_full[].city</code></td><td>City name of the company location</td><td>String</td></tr><tr><td><code>company_locations_full[].state</code></td><td>State of the company location</td><td>String</td></tr><tr><td><code>company_locations_full[].street</code></td><td>Street address of the company location</td><td>String</td></tr><tr><td><code>company_locations_full[].zip_code</code></td><td>Postal or ZIP code of the company location</td><td>String</td></tr><tr><td><code>company_locations_full[].latitude</code></td><td>Geographic latitude coordinate of the company location</td><td>Double</td></tr><tr><td><code>company_locations_full[].longitude</code></td><td>Geographic longitude coordinate of the company location</td><td>Double</td></tr></tbody></table>
{% endupdate %}

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

## Multi-source Employee data: adding new fields

### Adding new fields&#x20;

Adding new fields to surface academic background, career trajectory, and activity signals.

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>institution_ranking_score</code></td><td>Highest QS university ranking score across the employee's education institutions, matched by normalized institution name. <code>null</code> if no institution matches</td><td>Double</td></tr><tr><td><code>months_in_management</code></td><td>Total months spent in management-level roles. Calculated as the union of these positions, so overlapping roles aren't counted twice</td><td>Long</td></tr><tr><td><code>post_frequency_yearly</code></td><td>Count of professional network posts over the past 12 months</td><td>Double</td></tr><tr><td><code>posting_recency</code></td><td>Date of the employee's most recent post</td><td>Date</td></tr><tr><td><code>engagement_per_post</code></td><td>Average engagement (reactions and comments) per post</td><td>Double</td></tr><tr><td><code>influence_score</code></td><td>Composite 0–100 social-influence score: a weighted, log-scaled blend of post frequency (0.2), engagement per post (0.5), and follower count (0.3), each capped at a fixed, precomputed 99th-percentile threshold. Defaults to <code>0.0</code></td><td>Double</td></tr><tr><td><code>activity[].created_at</code></td><td>Creation timestamp of the activity item</td><td>Timestamp</td></tr><tr><td><code>activity[].updated_at</code></td><td>Last-updated timestamp of the activity item</td><td>Timestamp</td></tr></tbody></table>

### Adding a `tenure_stats` struct

A new nested struct capturing per-company tenure statistics in months, derived from the employee's company-linked experience.

| Data field                       | Description                                                                                                                                                                                                                                              | Data type |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| `tenure_stats`                   | Per-company tenure statistics in months, with concurrent roles at the same company counted once. It presents raw data without plausibility checks, so some values might be unrealistic. `null` if the employee has no datable, company-linked experience | Struct    |
| `tenure_stats.avg_tenure_months` | Average total tenure per company                                                                                                                                                                                                                         | Double    |
| `tenure_stats.median_tenure`     | Median total tenure per company                                                                                                                                                                                                                          | Double    |
| `tenure_stats.current_tenure`    | Tenure at the current (active) position. `null` if not currently employed                                                                                                                                                                                | Double    |
| `tenure_stats.longest_tenure`    | Longest total tenure at a single company                                                                                                                                                                                                                 | Double    |

### Adding a `internal_promotion_rate` struct

A new nested struct quantifying internal career progression. Promotions are inferred from position-title changes within the same company, ordered by start date.

| Data field                                         | Description                                                                                                                                                                                      | Data type |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
| `internal_promotion_rate`                          | Internal promotion metrics, derived from position-title changes within the same company, ordered by start date, counting only changes where the new role starts strictly after the previous role | Struct    |
| `internal_promotion_rate.promotion_count`          | Count of internal title changes (promotions). `0` if none                                                                                                                                        | Integer   |
| `internal_promotion_rate.avg_months_per_promotion` | Average months between consecutive promotions. `null` with fewer than two promotions                                                                                                             | Double    |
| `internal_promotion_rate.recently_promoted`        | True if a promotion occurred within the last 3 months                                                                                                                                            | Boolean   |
| {% endupdate %}                                    |                                                                                                                                                                                                  |           |

{% update date="2026-07-10" %}

## Company Posts API: adding new endpoints

We now offer access to Company Posts data through an API. Use the following endpoints to explore the data:

| Method | Endpoint                             |
| ------ | ------------------------------------ |
| POST   | `/v2/company_post/search/filter`     |
| POST   | `/v2/company_post/search/es_dsl`     |
| GET    | `/v2/company_post/collect/{post_id}` |

Find more information in [Company Posts API](/company-api/company-posts-api.md).
{% endupdate %}

{% update date="2026-07-27" %}

## Response headers changes

We are planning several updates to API response headers that could impact your workflows. See below for information on the affected response headers.

| Action                                       | Response header         | Notes                                                                                       |
| -------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------- |
| <mark style="color:$danger;">Removing</mark> | `x-subscription-active` | "x-subscription-active" response header will no longer be returned in API Search responses. |
| <mark style="color:$info;">Changing</mark>   | `x-credits-remaining`   | "x-credits-remaining" value will update to display all available data collection credits.   |
| {% endupdate %}                              |                         |                                                                                             |

{% update date="2026-07-27" %}

## Scheduled maintenance

Scheduled maintenance is planned for July 27th, from 8 to 10 AM EET. During this time, all API endpoints and the self-service dashboard will be temporarily unavailable. Any requests sent will receive a `503 Service Unavailable` error. Please plan your integrations accordingly.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coresignal.com/release-notes/july-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.