What This Means for Your API Integration

As part of the XMLRPC sunset, a small number of XMLRPC endpoints will not be directly converted to REST v2. If your integration uses any of these endpoints, your API calls will stop working on December 31, 2026 — the date all XMLRPC endpoints are being decommissioned. Review the list of affected endpoints below to determine whether your integration is impacted and what alternative approaches are available before that deadline.

Which Endpoints Are Not Being Converted

The Gap Analysis Justifications spreadsheet identifies every XMLRPC endpoint that will not be converted to REST v2. For each endpoint, the spreadsheet explains why a direct conversion is not being made and lists recommended alternative approaches where available. Download the spreadsheet, review the affected endpoints, and evaluate whether the suggested alternatives meet your integration needs.

Download the Gap Analysis Justifications spreadsheet — full list of deprecated XMLRPC endpoints and recommended REST v2 alternatives

What to Do If the Alternatives Do Not Meet Your Needs

If the recommended alternatives listed in the spreadsheet do not work for your integration, post your question in the Q&A forum and tag the API Specialist for direct assistance evaluating your options before the December 31, 2026 deadline.

Key Deadline to Know

December 31, 2026 — All XMLRPC endpoints, including the deprecated endpoints not being converted to REST v2, will stop working on this date. Any integration that has not migrated to REST v2 or an approved alternative by December 31, 2026 will experience API failures.