As part of our ongoing XML-RPC sunset and migration to REST v2, this document provides a detailed mapping between existing XML-RPC methods and their REST v2 resources. This guide is designed to help you quickly identify where each XML-RPC operation now lives within REST v2, making it easier to plan, implement, and validate your migration.

Why This Matters

The REST v2 API offers a modern, consistent, and more secure experience compared to XML-RPC. By using this mapping, you can:

• Understand which REST v2 resources to replace your current XML-RPC calls.
• Simplify your migration planning by seeing all equivalents in one place.
• Reduce the risk of disruption as XML-RPC services are phased out.

How to Use This Document

Each row in the mapping table shows:

• The Domain (e.g., Affiliates, CRM)
• The XML-RPC resource and operation (Create, Get, List, etc.).
• The corresponding REST v2 resource you should now use.

Use this as a reference during your migration process to ensure that all XML-RPC dependencies are fully replaced with REST v2 equivalents.

If you find a method without a direct REST v2 equivalent, please check the “XML-RPC Methods Not Being Converted to v2” help article for details. If it’s not listed there, reach out to our API Specialist, Omar Almonte, through the Developer Forum for assistance.

Find the mapping document here: XML-RPC to REST v2 Mapping.xlsx