We don't have a list of APIs we plan to deprecate today, because deprecation is not removal - deprecation is a plan to remove.
When we deprecate APIs it's because they were never intended to be public to begin with or a feature is being removed from the product entirely (e.g. media libraries) with a replacement (e.g. Content hub and content item assets).
If your team relies heavily on an API that we deprecate, please let us know by giving us product feedback. Tell us:
- Your business case for using the API (what type of project feature it enables)
- Other APIs or features you tried to use to accomplish the same goal
This feedback helps us understand what type of replacement API we could design or how we could enable the same use case with a new or updated product feature.
As Liam mentioned, deprecated APIs are listed in the changelog. If we have a simple clear replacement, it will be listed there.
We typically remove deprecated APIs during a major version change, and historically we've had about one of these each year around December.
When updating your Xperience projects to the latest Refresh, have an AI agent review the build output for deprecation warnings, search the changelog for details about the deprecation, and then write a short report explaining the impacted areas of your project and how to resolve the warnings. In my experience, the agent can typically also resolve the build warning.