Can I Deprecate or Disable Legacy REST API Endpoint URLs in Decisions (v9.11) So They Return 404?

RichterBell

Hello,

We have several flows in Decisions that were exposed as REST API endpoints before version 9.11, resulting in legacy URLs that are still accessible. We want to deprecate these old endpoints so that any requests to them return a 404 error. Is there a way to disable or invalidate these legacy REST API URLs? Any advice or best practices would be appreciated!

MalikBackman_Decisions

Hello,

Currently, Decisions does not have a built-in feature to directly deprecate or disable legacy REST API endpoint URLs. Changing the Element Slug does not invalidate existing links, so old URLs remain active. Here are your options:

• Move the Flow to a different project. This will break the existing endpoint links, but you’ll need to update any dependencies.

• Create a new Flow and delete the original. This invalidates the previous URLs, but you’ll need to redirect any integrations to the new endpoint.

Before making changes, always test in a lower environment and take a full database backup before updating production.

If neither option fits your needs, consider submitting a feature request to Decisions Customer Support with details about your use case and the impact on your environment.