Skip to main content

​
Deprecation of publisher_errors endpoint

Communicated on: April 15, 2026
Application date: October 15, 2026 The POST /publisher_errors/{business_id} endpoint has been deprecated in favor of the new POST /diffusion_errors/{business_id} endpoint. What’s changing: 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: 
POST /publisher_errors/{business_id}
To: 
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): 
{
  "errors": [
    {
      "publisher_id": "google",
      "error_code": "le118000",
      "field": "invalid_field",
      "message": "Field validation failed"
    }
  ]
}
New Response Format (diffusion_errors): 
{
  "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 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.