# March 2025

## Indeed Company data

### 🔄 Field replacement: Website links

**Effective from:** March 2025

| Action  | Data field | Description                  | Type             |
| ------- | ---------- | ---------------------------- | ---------------- |
| Removed | `links`    | Various company websites     | Array of strings |
| Added   | `link`     | Primary company website link | String           |

**Impact:**\
Only the main website URL will now be returned. This simplifies downstream usage and aligns with improved field standards.

## Craft data

### ❌ Field removal: Craft News section

**Effective from:** March 2025

**Reason:**\
The Craft source no longer provides public access to News content. We are evaluating potential alternatives to restore this capability.

| Action  | Data field     | Description                          | Type             |
| ------- | -------------- | ------------------------------------ | ---------------- |
| Removed | `news`         | News articles related to the company | Array of objects |
| Removed | `headline`     | Article headline                     | String           |
| Removed | `image_url`    | Article image URL                    | String           |
| Removed | `summary`      | Article summary                      | String           |
| Removed | `published_at` | Article publish date (YYYY-MM-DD)    | String (date)    |
| Removed | `url`          | URL to the full article              | String           |

## Clean Company data and Clean Company API

### 🆕 New field: `company_websites_professional_network_canonical`

**Formats:** Flat files and API\
**Effective from:** March 3, 2025

| Action | Data field                                        | Type   | Description                                |
| ------ | ------------------------------------------------- | ------ | ------------------------------------------ |
| Added  | `company_websites_professional_network_canonical` | String | Canonical professional network profile URL |

**Reference:**\
Learn more in [Clean Company Data dictionary](/company-data/clean-company-data/dictionary-clean-company-data.md) or [Clean Company API dictionary](/company-api/clean-company-api/data-dictionary-clean-company-api.md).

## Employee data

### 🔁 Field rename

| Action  | Old Name    | New Name    | Description                         | Type             |
| ------- | ----------- | ----------- | ----------------------------------- | ---------------- |
| Renamed | `member_id` | `parent_id` | Employee profile identification key | Number (integer) |

***

### 🆕 New field

| Action | Field Name  | Description                                                | Type             |
| ------ | ----------- | ---------------------------------------------------------- | ---------------- |
| Added  | `is_parent` | Indicates if the ID is the original (non-duplicate) record | Number (integer) |

***

### ⏳ Scheduled removals (May 2025)

| Action                | Field Name    | Description                                          | Type             |
| --------------------- | ------------- | ---------------------------------------------------- | ---------------- |
| Scheduled for removal | `is_latest`   | Original and active record indicator (now redundant) | Number (integer) |
| Scheduled for removal | `received_at` | Internal operations field; use `updated_at` instead  | Timestamp        |

## Search API endpoints

### 🔁 Updated ID ordering logic in Search API

**Effective Date:** March 19, 2025\
**Change Summary:**

* **Previous default:** Ascending by `id`
* **New default:** Descending by `last_updated`, then by `id`

***

#### 📦 Pagination format updates

**🔹 Search Filter endpoints**

| Before (x-next-page-after) | After              |
| -------------------------- | ------------------ |
| `123`                      | `"2025-01-01",123` |

**Note:** Use `?sort=id` to preserve previous ID-based sorting behavior.

**🔹 Elasticsearch DSL endpoints**

| Before (x-next-page-after) | After                    |
| -------------------------- | ------------------------ |
| `0.345,123`                | `0.345,"2025-01-01",123` |

**Note:** Pass `"sort": ["id"]` in the request body to retain previous logic.

***

#### 🔄 Backwards compatibility options

| Type              | Option                                 |
| ----------------- | -------------------------------------- |
| Search Filter     | Add query parameter `?sort=id`         |
| Elasticsearch DSL | Use `{"sort": ["id"]}` in request body |

## Clean Employee API

### 🆕 New data field: `date_day`

**Release date:** March 26, 2025

| Action | Field Name | Type   | Description                 |
| ------ | ---------- | ------ | --------------------------- |
| Added  | `date_day` | String | Day of the award issue date |

**Schema context:**\
This field is now part of the nested `awards` object in the Elasticsearch DSL schema and enables more granular filtering or sorting based on exact award dates. Input type is `byte`.


---

# 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/march-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.