# July 2025

## Multi-source Company data and **Multi-source Company API**

### ⚠ Breaking changes

**Field key updates for review distributions**:

* `product_reviews_score_distribution`: Renamed struct keys from numeric (`1–5`) to `score_1–score_5`.
* `employee_reviews_score_distribution`: Renamed struct keys from numeric (`1–5`) to `score_1–score_5`.

### 🐞 Bug fixes

**Date field correction**: 

Fixed issues with invalid string date values (e.g., years starting with "0" or exceeding "9999").

* `acquisition_list_source_1.announced_date`
* `acquisition_list_source_5.announced_date`<br>

## :new: Employee Posts data and Employee Posts API

### ✨ New features

* Enables structured retrieval and querying of employee-generated posts.
* Supports filtering by author, content, date, and more.
* Built on Elasticsearch for fast, scalable querying.

### **🔹 Endpoints**

#### **Search**:

* `POST /v2/post_employee/search/es_dsl`
* `POST /v2/post_employee/search/filter`

#### **Collect**:

* `GET /v2/post_employee/collect/{post_id}`

Each post includes metadata such as author info, post content, date, mentions, and engagement data (e.g., comments and reactions).


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.