This article covers how to find the REST v2 equivalent for each XML-RPC method you're currently using, so you can plan and validate your migration. This article does not cover the deprecation timeline itself or what changes on the deprecation date — see the linked article below for that.

In this article:

• Why This Mapping Guide Matters
• How to Use the Mapping Document
• If a Method Has No Direct REST v2 Equivalent
• What This Article Does Not Cover

Why This Mapping Guide Matters

As part of the ongoing XML-RPC deprecation and migration to REST v2, this guide provides a detailed mapping between existing XML-RPC methods and their REST v2 resources. Keap's XML-RPC API will be deprecated without warranty or support starting March 15, 2027. For full details on what changes on that date, see Keap XML-RPC API Deprecation: Updated Date and Migration to REST v2.

REST v2 offers a more modern, consistent, and secure experience than XML-RPC. Using this mapping guide helps you identify which REST v2 resource replaces each XML-RPC call you're currently making, plan your migration by seeing all the equivalents in one place, and reduce the risk of disruption once XML-RPC is deprecated without warranty or support.

How to Use the Mapping Document

The mapping document is organized as a table. Each row in the table shows the domain the method belongs to (for example, Affiliates or CRM), the XML-RPC resource and operation (Create, Get, List, and so on), and the corresponding REST v2 resource you should use instead.

Use the mapping document as a reference throughout your migration to confirm that every XML-RPC method your integration calls has been replaced with its REST v2 equivalent. You can find the mapping document here: XML-RPC to REST v2 Mapping.xlsx.

If a Method Has No Direct REST v2 Equivalent

If you find an XML-RPC method in the mapping document without a direct REST v2 equivalent, check the "XML-RPC Methods Not Being Converted to v2" help article for details on that specific method. If the method isn't listed there either, reach out to Keap's API Specialist, Omar Almonte, through the Developer Forum for assistance.

What This Article Does Not Cover

This article covers how to use the XML-RPC to REST v2 mapping document to plan your migration. This article does not cover the deprecation date, what "deprecated without warranty or support" means, or what happens if your integration fails after the deprecation date — see Keap XML-RPC API Deprecation: Updated Date and Migration to REST v2 for those details.