Contents
Changelog
August 29, 2022
Announced: June 29, 2022
August 29, 2022
UPDATE: The implementation of this change has been delayed for existing customers prior to August 29, 2022. We apologize for any confusion or inconvenience this has caused. From August 21, 2023, we are starting the rollout of this change. Please refer to the updated announcement in Changelog for further details.
We are applying limits to filter conditions and removing 3 conditions from the Filters API to ensure a reliable experience and quick responses for all users.
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)
The new limit and removal of the 3 conditions will go into effect on August 29, 2022. We advise you to review the filters you have created and make sure that they adhere to the changes.
Why is it changing?
We've added new limits to the Filters API because complex filters can easily cause system overload. As we are constantly improving our systems, these limits will help to continuously support the excellent performance of our API to apps and users.
Who will be affected?
Everyone who is using the specified POST
and PUT
endpoints to add and/or modify filters or has filters with more than 16 conditions in place.
If you have any questions or comments, let us know in the Developer’s Community.