@OmarAlmonte - Another suggestion for you. Can your team implement an interface within the Keap application so that customers / developers see the XML-RPC API calls being done with statistics.
Last year i suggested something similar when the Legacy API Key was being sunset. But your predecessors were too stubborn in helping out developers. It required having to contact the support team to get the API call logs to see if the key was still being used in integrations.
Transition from XML-RPC to REST is going to be a major job for some developers, depending on the complexity of things. Being able to easily see the calls will help identify things and to see if the transition has been achieved as well. It will save time having to go backwards and forwards with support in the future.
While Keap doesn’t currently have a built-in interface to view XML-RPC API calls with statistics, there are a couple of resources that can help you track and analyze your integrations. You can check out our Help Article on Identifying XML-RPC Integrations for detailed guidance.
Additionally, our Migration Guide from XML-RPC to v2 includes a Python script that scans your project and exports matches to a CSV for easy analysis. The planned brownouts also help by highlighting any remaining XML-RPC usage during the transition.
These tools should give you the visibility needed to track usage and make the transition to V2 smoother.
That is only good enough if developers are actively maintaining the integrations and are aware about the sunset.
Some of your customers will have XML-RPC integrations that could be running for years without any updates. If the developers are no longer around, then the customers will not know any different.
Something will need to be added to help out sooner rather than later. Otherwise if customers get informed too late, then the developers may not have enough time to update the code.
The Legacy API Key sunset communication was a mess, those mistakes need to be avoided this time around.
Exactly, that’s precisely the value of the brownouts. Their purpose is to alert customers of any remaining XML-RPC usage, even if the original developers are no longer maintaining the integrations. This way, customers can proactively identify which integrations are still active before the final transition.
One reason is that they can disrupt businesses unless they opt out.
Second reason It does not necessary guarantee that a brownout will help. Some integrations can vary in usage. Say an integration only does around 100+ XML-RPC API calls scattered throughout the month. Those calls could completely miss the brownouts and the customer will none be the wiser.
I still suggest that you give customers visual way to see the XML-RPC API Calls, otherwise it will be a repeat of asking the support teams for information.