With the announcement of the XML-RPC sunset, we understand that reviewing existing integrations can feel challenging. Keap is not able to directly see which integrations are installed in your app, similar to how a mobile phone company may not know every app you have on your phone. To view your Keap integrations installed, you'll need to check in your Keap settings.

Planned Brownouts of XML-RPC endpoints

These large-scale technical migrations sometimes require brief, intentional system slowdowns, which we refer to as "brownouts." While these events can feel disruptive, they serve an important purpose. This process is designed to:

• Ensure Stability: The migration strengthens the reliability of your connected services, preventing unexpected issues later. The brownouts serve to validate whether any part of your system is still relying on XML-RPC. 

• Future-Proof Your Business: The upgrade provides a faster, more robust framework for all future features and integrations.

• Maintain Service: We manage these temporary events to minimize impact, ensuring a quick and seamless transition to the new, enhanced system

If an integration or workflow fails during a brownout, it’s a strong indicator that XML-RPC calls are still in use and should be reviewed as part of your migration plan. This gives you the opportunity to identify issues early, long before the final sunset date, and ensure a smooth and predictable transition to REST v2.

To help you plan accordingly, you can review the full brownout schedule here. These brownouts are designed as a safety net to help teams confirm readiness, avoid last-minute surprises, and move confidently toward full adoption of the upgraded API endpoints.

How to Identify Integrations Affected by Brownouts

This article is provided to help identify any integrations that may be affected, including custom integrations or code that has been added. The brownouts will also help highlight any integrations still using XML-RPC, giving an extra layer of visibility as you review your setup.

How to Review Your Integrations in Keap Pro, Max, and Ultimate

To help identify which integrations may be affected by the XML-RPC sunset, you can review your current setup directly in the app. This process works together with the brownouts to surface any legacy XML-RPC activity.

1. Access your API settings

a. Click on your profile name in the app.

b. Select Settings from the menu.

c. Scroll down and choose API.

2. Explore the available tabs and identify integrations

At the top of the API page, you’ll see three tabs:

a. Third-Party Authorizations: Shows integrations that are using our approved OAuth2.0 authentication method. For each integration, you can see the app name and who authorized it, making it easier to identify active integrations.

b. Personal Access Tokens (PATs): Lists tokens created by the currently logged-in user for integrations not using OAuth2.0. For each token, you’ll see the name and date created. PATs do not show who is using them.

c. Service Account Keys (SAKs): Lists keys created for service accounts or programmatic access. For each key, you’ll see the name and date created. SAKs can only be viewed by admins and do not show who is using them.

How to Review Your Integrations in Max Classic

To help identify which integrations may be affected by the XML-RPC sunset, you can review your current setup directly in the app. This process works together with the brownouts to surface any legacy XML-RPC activity.

1. Access your API settings

a. Click the profile icon in the navigation bar

b. Select API Settings from the menu

2. Explore the available tabs and identify integrations

In this page you’ll see:

a. Third-Party Authorizations: Shows integrations that are using our approved OAuth2.0 authentication method. For each integration, you can see the app name and who authorized it, making it easier to identify active integrations.

b. Personal Access Tokens (PATs): Lists tokens created by the currently logged-in user for integrations not using OAuth2.0. For each token, you’ll see the name and date created. PATs do not show who is using them.

c. Service Account Keys (SAKs): Lists keys created for service accounts or programmatic access. For each key, you’ll see the name and date created. SAKs can only be viewed by admins and do not show who is using them.

Reviewing Your Results

While these tabs won't directly tell you whether an integration is using XML-RPC, they do give you a clear inventory of all integrations, tokens, and keys currently connected to your Keap app. This list is an important starting point as you review which integrations may need attention or updates.

We also provide an Integrator Status Report, available here.

Some integrators choose to share their migration progress in this document, so you can easily follow their status. Please note that participation is optional, so if an integrator doesn’t appear in the report, we recommend reaching out to them directly to confirm their current migration plans.

Identifying XML-RPC Usage in Custom Integrations

If your account uses a custom-built integration and you have access to the project’s source code, you can review your codebase to identify any XML-RPC calls. To make this easier, we’ve included a ready-to-use Python script in the full migration guide. The script scans your project recursively, skips common dependency and build folders, and exports any detected XML-RPC references into a CSV file for quick review.

For a complete step-by-step walkthrough of how to migrate from XML-RPC to the REST v2 API, including the Python script, you can access the full guide here.

FAQ

Why is this API migration necessary?

We are migrating to a modern, more robust system architecture. This upgrade is essential to guarantee the long-term speed, security, and stability of the integrated tools you rely on (such as scheduling, payment gateways, and marketing connections). This work future-proofs your service and supports new features.

What should I do if my integration is failing during a scheduled brownout?

If an integration fails or times out during the scheduled date and time, please wait until the brownout window has passed and try the action again. These events are intentionally brief, and the service should restore automatically once the migration step is complete.