Filters will no longer be returned from the Lists API
UPDATE: After hearing feedback from you, our community of developers, there were some use cases we hadn’t taken into account. In order to make sure we can thoughtfully consider our approach to the List filter migration we are going to pause the change to remove the filters for the time being. We will update this thread again when we have more information. Please feel free to continue to add use cases and ask questions.
When getting Lists via the API, you will no longer be able to get the filters that populated that list. Instead you will see an empty array in the filters field. This does not affect your ability to create new lists and define filters then.
Why is this happening?
In order to support an upcoming migration we need to translate filters between the old system and new system. While the system keeps all the functionality of the old system, while adding more, not all filters can be translated back into the old ones.
When is this happening?
This change will go live in 2 weeks on August 3rd.
If you have any questions or concerns, don’t hesitate to join the conversation in the community.