On June 29, 2022, we announced the breaking changes in filter conditions for Filters API. The end date of the warning period has passed without the change going live for existing users prior to the initial announcement date. We want to apologize for any confusion or inconvenience this has caused.

The changes to filter conditions will be implemented for all users between August 21 and September 3, 2023. All the details from the original announcement remain:

What is changing?

We will be implementing a limit to the number of conditions a filter can have via the POST /filters and PUT /filters/{id} endpoints. The new limit will be 16 conditions per filter.

If a filter is being added or updated to include more than 16 conditions, the request will fail and a 400 error response, similar to this one, will be returned:

{
  "success": false,
  "error": "Filter is allowed to have at most 16 conditions",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API.",
  "data": null,
  "additional_data": null
}

In addition to the limit, we have now deprecated and will soon stop supporting the following filter conditions from the conditions body parameter of the POST /filters and PUT /filters/{id} endpoint:

• LIKE '%$' (ends with)
• NOT LIKE '%$%' (does not contain)
• NOT LIKE '%$' (does not end with)

We advise you to review the filters you have created and make sure that they adhere to the changes.

All existing filters with more than 16 conditions and/or the unsupported conditions will remain usable, but cannot be edited until they meet the above-mentioned requirements.

Why is it changing?

Complex filters can easily cause system overload. As we are constantly improving our systems, these limits will help to continuously support the performance of our API to apps and users.

If you have any questions or comments, let us know in the Developers' Community.