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

# September 2026

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

## Multi-source Company data: adding new fields

We are adding fields for data quality, company identity, location, and company relationships. Use them to keep records current and enrich company profiles with related companies and employees.

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>is_deleted</code></td><td>Record deletion status:<br><code>1</code> – the profile returned "Page not found" or was deleted;<br><code>0</code> – the record exists</td><td>Integer</td></tr><tr><td><code>quality</code></td><td><p>Indicates record quality:</p><p><code>1</code> – the record meets all of the following:</p><ul><li>A company name is present;</li><li>Contains at least one indicator of identity: a website, company logo, or a non-zero number of employees;</li><li>The record has been updated recently enough to be considered current.</li></ul><p><code>0</code> – one or more of those checks failed</p></td><td>Integer</td></tr><tr><td><code>professional_network_shorthand_names</code></td><td>Historical variations of shorthand names for the company</td><td>Array of strings</td></tr><tr><td><code>tagline</code></td><td>Company tagline/headline as displayed on Professional network</td><td>String</td></tr><tr><td><code>company_locations_full.country</code></td><td>Location country</td><td>String</td></tr><tr><td><code>company_locations_full.country_iso_2</code></td><td>ISO 2-letter code of the country</td><td>String</td></tr><tr><td><code>company_locations_full.country_iso_3</code></td><td>ISO 3-letter code of the country</td><td>String</td></tr><tr><td><code>company_locations_full.regions</code></td><td>Location regions</td><td>Array of strings</td></tr></tbody></table>

**Adding `similar_pages` struct**

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>similar_pages</code></td><td>Companies similar to the record company</td><td>Array of structs</td></tr><tr><td><code>similar_pages[].id</code></td><td>Identification key for the similar company record</td><td>String</td></tr><tr><td><code>similar_pages[].name</code></td><td>Similar company name</td><td>String</td></tr><tr><td><code>similar_pages[].industry</code></td><td>Similar company industry</td><td>String</td></tr><tr><td><code>similar_pages[].url</code></td><td>Similar company profile URL</td><td>String</td></tr><tr><td><code>similar_pages[].location</code></td><td>Similar company location</td><td>String</td></tr></tbody></table>

**Adding `featured_employees` struct**

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>featured_employees</code></td><td>List of featured employees</td><td>Array of structs</td></tr><tr><td><code>featured_employees[].id</code></td><td>Identification key for the employee record</td><td>String</td></tr><tr><td><code>featured_employees[].full_name</code></td><td>Employee full name</td><td>String</td></tr><tr><td><code>featured_employees[].headline</code></td><td>Employee profile headline</td><td>String</td></tr><tr><td><code>featured_employees[].profile_url</code></td><td>Employee profile URL</td><td>String</td></tr></tbody></table>

**Adding `affiliated_pages` struct**

<table data-search="false"><thead><tr><th>Data field</th><th>Description</th><th>Data type</th></tr></thead><tbody><tr><td><code>affiliated_pages</code></td><td>Profiles of affiliated companies</td><td>Array of structs</td></tr><tr><td><code>affiliated_pages[].id</code></td><td>Identification key for the affiliated company record</td><td>String</td></tr><tr><td><code>affiliated_pages[].affiliated_company_id</code></td><td>Identification key relating to the company table for the affiliate company</td><td>Integer</td></tr><tr><td><code>affiliated_pages[].url</code></td><td>Affiliate company profile URL</td><td>String</td></tr><tr><td><code>affiliated_pages[].name</code></td><td>Affiliate company name</td><td>String</td></tr><tr><td><code>affiliated_pages[].location</code></td><td>Affiliate company location</td><td>String</td></tr><tr><td><code>affiliated_pages[].industry</code></td><td>Affiliate company industry</td><td>String</td></tr></tbody></table>
{% endupdate %}

{% update date="2026-09-15" %}

## Multi-source Company data: adding new fields

We are adding fields that describe what a company does and how it operates. Use them to classify companies by business area, offerings, SaaS status, and business model.

| Data field       | Description                                                                                                                                                       | Data type        |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
| `business_areas` | Mid-level areas the company operates in, e.g., what the company does                                                                                              | Array of strings |
| `offerings`      | Concrete products and services the company sells. Brand, product, and feature names are excluded                                                                  | Array of strings |
| `is_saas`        | Whether the company is a SaaS company                                                                                                                             | Boolean          |
| `business_model` | <p>Business model(s) the company operates in. <br>Possible values: <code>B2B</code>, <code>B2C</code>, <code>B2G</code>, <code>B2B2C</code>, <code>C2C</code></p> | Array of strings |
| {% endupdate %}  |                                                                                                                                                                   |                  |

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

## New field `processed_at`: adding across multiple datasets

A new field, `processed_at`, is being added to multiple datasets. This field records the timestamp of the last processing by the data pipeline before delivery, providing consumers with a delivery-side marker for when a record was prepared, independent of source-side collection or update timestamps.

| Data field     | Description                                                                                                                                        | Data type |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| `processed_at` | Exposes when data was processed on our side (reparsing, reloads, data quality fixes). Aligned to the delivery date – one day ahead of `updated_at` | Timestamp |

**Sources and affected entities**

<table data-search="false"><thead><tr><th width="200.23046875">Source</th><th>Entities</th></tr></thead><tbody><tr><td>Base Jobs</td><td>Jobs</td></tr><tr><td>Base Company</td><td>Company</td></tr><tr><td>Company Posts</td><td>Posts</td></tr><tr><td>Employee Posts</td><td>Posts</td></tr><tr><td>Craft</td><td>Company</td></tr><tr><td>Indeed</td><td>Jobs</td></tr><tr><td>Glassdoor</td><td>Jobs,<br>Review</td></tr><tr><td>Owler</td><td>Company</td></tr></tbody></table>
{% endupdate %}

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

## Company Posts data: removing a field

We are removing the `reshared_post.author_headline` field due to its low fill rate.

### Removing a field

<table data-search="false"><thead><tr><th>Data field</th><th>Data type</th></tr></thead><tbody><tr><td><code>reshared_post.author_headline</code></td><td>String</td></tr></tbody></table>
{% endupdate %}

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

## Multi-source Company API: adding new fields

We are introducing new fields to detail what a company does and how it functions. Utilize these fields to categorize companies based on their business area, offerings, SaaS status, and business model.

| Data field       | Description                                                                                                                                                       | Data type        |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
| `business_areas` | Mid-level areas the company operates in, e.g., what the company does                                                                                              | Array of strings |
| `offerings`      | Concrete products and services the company sells. Brand, product, and feature names are excluded                                                                  | Array of strings |
| `is_saas`        | Whether the company is a SaaS company                                                                                                                             | Boolean          |
| `business_model` | <p>Business model(s) the company operates in. <br>Possible values: <code>B2B</code>, <code>B2C</code>, <code>B2G</code>, <code>B2B2C</code>, <code>C2C</code></p> | Array of strings |
| {% endupdate %}  |                                                                                                                                                                   |                  |

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

## Webhooks: new response header

`GET /v2/subscriptions` endpoint now includes an `x-total-subscriptions` header in its response. Use this header to track your active subscriptions and stay within your subscription limit, eliminating the need to paginate through the entire list.

| Query                     | Header value                                      | Notes                                                        |
| ------------------------- | ------------------------------------------------- | ------------------------------------------------------------ |
| `expired=false` (default) | Count of subscriptions with `"status": "active"`  | This is the number to watch against your subscription limit  |
| `expired=true`            | Count of all subscriptions, expired ones included | Reading this value as your active count will overstate usage |
| {% endupdate %}           |                                                   |                                                              |

{% update date="2026-09-16" %}

## Webhooks: adding a new update endpoint

We are introducing a new `PATCH /v2/subscriptions/{subscription_id}` endpoint that enables you to add or remove IDs under an existing subscription without the need to create a new one. Read more in [Subscription Management](/api-introduction/webhooks/subscription-management.md) topic.
{% 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/september-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.