> ## Documentation Index
> Fetch the complete documentation index at: https://developers.partoo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Breaking Changes

> This page provides information about breaking changes to the API.

{/* <Note>
**🟢 No Upcoming Breaking Changes**           

If you don’t see any **breaking changes** listed on this page, that’s **normal**.  
It simply means there are no upcoming **breaking changes** or required **updates** for the next few months.
</Note> */}

## Deprecation of publisher\_errors endpoint

*Communicated on: April 15, 2026*\
*Application date: October 15, 2026*

The [`POST /publisher_errors/{business_id}`](/api-reference/presence/publishererrors-deprecated) endpoint has been deprecated in favor of the new [`POST /diffusion_errors/{business_id}`](/api-reference/presence/get-diffusion-errors-for-a-business) endpoint.

**What’s changing:**

* The old [`POST /publisher_errors/{business_id}`](/api-reference/presence/publishererrors-deprecated) endpoint is now marked as deprecated
* Please migrate to the new [`POST /diffusion_errors/{business_id}`](/api-reference/presence/get-diffusion-errors-for-a-business) endpoint

**Why this change:**

* Better organization and consolidation of publisher error handling endpoints
* Improved feature control with proper authorization checks
* More comprehensive error handling and validation

**Migration guide:**

Update your API calls from:

```bash theme={null}
POST /publisher_errors/{business_id}
```

To:

```bash theme={null}
POST /diffusion_errors/{business_id}
```

**Important:** The response structure has changed. The new endpoint provides errors grouped by publisher with enhanced categorization (pre-check and post-check errors). Please review the examples below:

**Old Response Format (publisher\_errors):**

```json theme={null}
{
  "errors": [
    {
      "publisher_id": "google",
      "error_code": "le118000",
      "field": "invalid_field",
      "message": "Field validation failed"
    }
  ]
}
```

**New Response Format (diffusion\_errors):**

```json theme={null}
{
  "diffusion_errors": {
    "google": {
      "pre_check_errors": [
        {
          "error_code": "le118000",
          "field": "invalid_field",
          "message": "Field validation failed"
        }
      ],
      "post_check_errors": []
    }
  }
}
```

Review the [diffusion errors endpoint documentation](/api-reference/presence/get-diffusion-errors-for-a-business) for complete details on the new response structure.

## Removing `phone` and `keywords` fields from user endpoints

*Application date: January 15, 2026*

We are removing `phone` and `keywords` fields from all user-related endpoints. Customers using these fields should update their integrations accordingly.

## Image message sending via direct upload

*Application date: January 15, 2026*

We are changing how image messages are sent via the API.

**What’s changing:**

* Image messages can no longer be sent using **direct file uploads (form-data)** through:\
  `POST /v2/messages`
* Instead, you must use **public URLs** to upload images.

**Who is affected:**

* Businesses sending messages via the message API
* Anyone uploading image messages via direct file upload

**Why this change:**

* This harmonizes how media is handled across the API and ensures consistent processing of image messages.