This article covers how to identify integrations in a Keap™ account that may be affected by the XML-RPC API sunset, including how to review API settings in Keap Pro, Max, and Ultimate, and in Max Classic. It also explains what brownouts are, how to interpret API settings results, and how to identify XML-RPC usage in custom integrations.
Keap cannot directly identify which integrations are installed in an account. To review installed integrations, check the API settings within the Keap application as described below.
Planned Brownouts of XML-RPC Endpoints
During the XML-RPC migration, brief intentional service slowdowns — referred to as brownouts — are used to validate whether any part of an account's setup is still relying on XML-RPC. These brownouts serve to:
Ensure stability — The migration strengthens the reliability of connected services. Brownouts surface any remaining XML-RPC dependencies before the final sunset date.
Future-proof integrations — The upgrade provides a faster, more robust framework for all future features and integrations.
Minimize disruption — Brownout events are managed to be brief, with service restoring automatically once each migration step is complete.
If an integration or workflow fails during a brownout, this indicates that XML-RPC calls are still in use and should be addressed as part of the migration plan. This provides an opportunity to identify issues early, before the final sunset date, and ensure a smooth transition to REST v2.
For dates and timing, see the full XML-RPC brownout schedule.
How to Identify Integrations Affected by Brownouts
The steps below explain how to review API settings in Keap to identify which integrations are connected to the account. Reviewing this list alongside brownout activity helps identify integrations still using XML-RPC.
Keap Pro, Max, and Ultimate
-
Select the profile name in the app.
The screenshot above shows the profile name in the Keap navigation bar.
-
Select Settings from the menu.
The screenshot above shows the Settings option in the Keap profile menu.
-
Scroll down and select API.
The screenshot above shows the API option in Keap Settings.
-
Review the three tabs at the top of the API page:
Third-Party Authorizations — Displays integrations using OAuth 2.0 authentication. Each entry shows the app name and the user who authorized it.
Personal Access Tokens (PATs) — Lists tokens created by the currently logged-in user for integrations not using OAuth 2.0. Each entry shows the token name and date created. PATs do not indicate which integration is using them.
Service Account Keys (SAKs) — Lists keys created for service accounts or programmatic access. Each entry shows the key name and date created. SAKs are only visible to admins and do not indicate which integration is using them.
The screenshot above shows the three tabs on the Keap API settings page.
Max Classic
-
Select the profile icon in the navigation bar.
The screenshot above shows the profile icon in the Keap Max Classic navigation bar.
-
Select API Settings from the menu.
The screenshot above shows the API Settings option in the Keap Max Classic profile menu.
-
Review the available tabs on the API Settings page:
Third-Party Authorizations — Displays integrations using OAuth 2.0 authentication. Each entry shows the app name and the user who authorized it.
Personal Access Tokens (PATs) — Lists tokens created by the currently logged-in user for integrations not using OAuth 2.0. Each entry shows the token name and date created. PATs do not indicate which integration is using them.
Service Account Keys (SAKs) — Lists keys created for service accounts or programmatic access. Each entry shows the key name and date created. SAKs are only visible to admins and do not indicate which integration is using them.
The screenshot above shows the API Settings page in Keap Max Classic.
Interpreting the API Settings Results
The API settings tabs do not directly indicate whether an integration is using XML-RPC. They do provide a complete inventory of all integrations, tokens, and keys currently connected to the Keap account. This list is the starting point for identifying which integrations may need to be reviewed or updated before the XML-RPC sunset date.
An Integrator Status Report is also available to help track migration progress from third-party integration providers. See the Keap Integrator Status Report for a list of integrators and their current migration status. Participation in the report is optional — if an integrator does not appear, contact them directly to confirm their migration plans.
Identifying XML-RPC Usage in Custom Integrations
For accounts using a custom-built integration with accessible source code, the codebase can be reviewed to identify any XML-RPC calls. A ready-to-use Python script is available in the full migration guide that scans a project recursively, skips common dependency and build folders, and exports any detected XML-RPC references into a CSV file.
For a complete walkthrough of migrating from XML-RPC to the REST v2 API, including the Python script, see the XML-RPC to REST v2 migration guide.
Frequently Asked Questions
What does this article cover?
This article covers how to review API settings in Keap to identify connected integrations that may be affected by the XML-RPC sunset, what brownouts are, and how to identify XML-RPC usage in custom integrations.
Why is the XML-RPC API being sunset?
The migration to the REST v2 API moves Keap to a modern, more robust architecture that improves the long-term speed, security, and stability of connected tools such as scheduling, payment gateways, and marketing integrations. The upgrade also supports new features that are not available through XML-RPC.
What should be done if an integration fails during a brownout?
Wait until the brownout window has passed, then try the action again. Brownout events are intentionally brief and the service restores automatically once the migration step is complete. A failure during a brownout indicates that the integration is still using XML-RPC and should be prioritized in the migration plan.
Comments
0 comments