Keap XML-RPC API Deprecation: Updated Date and Migration to REST v2

This article covers the updated timeline for the Keap XML-RPC API deprecation, what "deprecated without warranty or support" means for your integration, and what to do to prepare. This article does not cover the technical steps for rebuilding an integration on REST v2 — that guidance comes from the integrator who built your integration.

In this article:

• What's Changing with the Keap XML-RPC API Deprecation Date
• What "Deprecated Without Warranty or Support" Means for Your Integration
• Why You Should Migrate to REST v2 Now
• How to Prepare for the Keap XML-RPC API Deprecation
• Frequently Asked Questions About the Keap XML-RPC API Deprecation
• What This Article Does Not Cover

What's Changing with the Keap XML-RPC API Deprecation Date

In a December 1, 2025 announcement about the Keap XML-RPC API sunset, Thryv stated that Keap's XML-RPC API would be permanently sunset on December 31, 2026. Thryv has updated this plan. Instead of a full sunset, Keap's XML-RPC API will be fully deprecated on March 15, 2027, without warranty or support.

The difference between these two terms matters. A sunset means the API stops working entirely on the stated date. Deprecation without warranty or support means the API keeps running past the stated date, but Keap stops maintaining it going forward.

What "Deprecated Without Warranty or Support" Means for Your Integration

Starting March 15, 2027, Keap will no longer provide updates or patches for the XML-RPC API, accept support tickets related to XML-RPC integrations, or answer questions about XML-RPC integrations. This includes outages related to the XML-RPC API. Keap will not troubleshoot or resolve an XML-RPC outage after March 15, 2027.

Your XML-RPC integration will continue to run past March 15, 2027. Keap is not shutting off access to the API on that date. The risk is what happens if your integration breaks after that date: if your XML-RPC integration fails after March 15, 2027, there is no fix coming from Keap. The only path forward at that point is migrating the integration to Keap's REST v2 API.

Why You Should Migrate to REST v2 Now

If your XML-RPC integration handles invoicing, contact syncing, appointment scheduling, or automation triggers, a failure after March 15, 2027 means that workflow stops with no support path to restore it. Migrating to REST v2 before that date protects your business from an unplanned outage with no fix available.

REST v2 is a rebuild, not a drop-in replacement. REST v2 uses a different API architecture than XML-RPC, so your integrator will need to rebuild the integration rather than apply a simple upgrade. Starting that conversation with your integrator now gives them time to plan the rebuild before support for XML-RPC ends.

How to Prepare for the Keap XML-RPC API Deprecation

Contact the integrator who built your XML-RPC integration and ask about their timeline for rebuilding it on Keap's REST v2 API. Keap does not build or support integrations directly, so your integrator is responsible for planning and executing the migration.

If your integrator does not have a REST v2 migration plan, treat that as a signal to push them for a timeline or to evaluate other integration options. Keap can confirm the deprecation date and the difference between XML-RPC and REST v2, but Keap cannot migrate your integration for you.

Frequently Asked Questions About the Keap XML-RPC API Deprecation

Has the Keap XML-RPC API deprecation date changed? Yes. The Keap XML-RPC API was originally set for a full sunset on December 31, 2026. The date is now March 15, 2027, and the change is from a sunset to a deprecation without warranty or support.

What is the difference between "sunset" and "deprecated without warranty or support"? A sunset means the Keap XML-RPC API stops working on the stated date. Deprecation without warranty or support means the API keeps working past that date, but Keap stops providing updates, patches, support tickets, or outage help.

Will my Keap XML-RPC integration stop working on March 15, 2027? No, not automatically. Your integration will keep running as-is on that date. The risk is that if your integration breaks after March 15, 2027, there is no fix coming from Keap.

What happens if my Keap XML-RPC integration fails after March 15, 2027? Keap will not repair it. The only path forward is migrating the integration to Keap's REST v2 API.

Does the Keap XML-RPC API deprecation include outages? Yes. Outages related to the Keap XML-RPC API are included in the deprecation. Keap will not troubleshoot or resolve XML-RPC outages after March 15, 2027.

Can I still get support for my Keap XML-RPC integration before March 15, 2027? Yes. Keap continues to provide support for XML-RPC integrations as normal until March 15, 2027.

What should I do right now about my Keap XML-RPC integration? Contact the integrator who built your integration and ask about their timeline for rebuilding it on Keap's REST v2 API.

What if my integrator does not have a REST v2 migration plan? Treat that as a signal to push your integrator for a timeline, or evaluate other integration options. Keap cannot build or support the migration on your integrator's behalf.

Is migrating to REST v2 a simple upgrade or a full rebuild? A full rebuild. Keap's REST v2 API uses a different architecture than XML-RPC, so it is not a drop-in replacement.

What This Article Does Not Cover

This article covers the Keap XML-RPC API deprecation date and what it means for existing integrations. This article does not cover the technical steps for rebuilding an integration on Keap's REST v2 API — that guidance comes from the integrator who built your integration, not from Keap support.