Skip to main content

Thryv XML-RPC API Deprecation: Updated Date and Trusted Migration Partners

Madsen, Amanda

This article covers the updated deprecation date for the Thryv XML-RPC API and where to find help if you don't know who built your integration. This article does not cover the technical steps for rebuilding an integration on REST v2 — that guidance comes from the integrator you choose to work with.

In this article:

What Changes on March 15, 2027

On December 1, 2025, Thryv communicated that the XML-RPC APIs would be permanently sunset on December 31, 2026. Thryv has revised that plan. Starting March 15, 2027, the XML-RPC APIs will be deprecated without warranty or support instead of fully sunset.

Your XML-RPC integration will keep running past March 15, 2027. Starting on that date, Thryv will no longer provide updates or patches for the XML-RPC APIs, accept support tickets related to XML-RPC integrations, or answer questions about XML-RPC integrations. This includes outages related to the XML-RPC APIs. If your XML-RPC integration fails after March 15, 2027, the path forward is rebuilding it on REST v2.

Why You Should Migrate to REST v2 Now

If your XML-RPC integration handles tasks like contact syncing, invoicing, or automated communication with your customers, a failure after March 15, 2027 means that task stops with no support available to fix it. Migrating to REST v2 before that date protects your business from losing a workflow you depend on with no path to restore it quickly.

REST v2 is a rebuild, not a simple update. REST v2 uses a different API architecture than XML-RPC, so migrating means having your integration rebuilt rather than upgraded. Starting the migration conversation now gives your integrator time to plan and test the rebuild before support for XML-RPC ends.

What to Do If You Don't Know Who Built Your Integration

If you're not sure who built your XML-RPC integration, or the person who built it is no longer active, Thryv has identified trusted integrators who can help you migrate to REST v2. You are not required to use an integrator from this list. You're free to work with any integrator of your choosing, including one not listed here. Thryv provides this list as a courtesy only.

Thryv does not take responsibility for the cost, time, or effort of migrating from XML-RPC to REST v2. Thryv does not set integrator pricing, provide quotes, or take part in pricing conversations with any integrator. Working with any integrator, whether from this list or elsewhere, is independent of your relationship with Thryv.

Trusted Integrators Who Can Help You Migrate

The following integrators can help you migrate your XML-RPC integration to REST v2:

Frequently Asked Questions About the Thryv XML-RPC API Deprecation

Has the Thryv XML-RPC API sunset date changed? Yes. The plan changed from a full sunset on December 31, 2026 to deprecation without warranty or support on March 15, 2027.

What does "deprecated without warranty or support" mean? Thryv keeps the XML-RPC APIs running past March 15, 2027, but stops maintaining them: no updates, no patches, no support tickets, and no outage help.

Will my XML-RPC integration stop working on March 15, 2027? Not automatically. Your integration keeps running as-is on that date. The risk is that if your integration breaks after March 15, 2027, Thryv will not fix it.

What happens if my XML-RPC integration fails after March 15, 2027? Thryv will not repair it. The only path forward is rebuilding the integration on REST v2.

Does the deprecation include outages? Yes. Outages related to the XML-RPC APIs are included after March 15, 2027.

Can I still get support for my XML-RPC integration before March 15, 2027? Yes. Support continues as normal until that date.

I don't know who built my integration. What do I do? Use the trusted integrator list in this article, or find your own integrator. You are not restricted to the integrators listed here.

Am I required to use one of the listed integrators? No. You can use any integrator, including one not on this list. The list is provided as a courtesy only.

Does Thryv set pricing or manage the relationship with these integrators? No. Thryv does not set pricing, provide quotes, or take part in that conversation. Working with any integrator is independent of your relationship with Thryv.

Is Thryv responsible for the cost or effort of migrating? No. Thryv does not take responsibility for the cost, time, or effort of migrating from XML-RPC to REST v2.

Is REST v2 a simple update or a rebuild? A rebuild. REST v2 is a different API architecture than XML-RPC, not a drop-in replacement.

What happens if I do nothing? Your XML-RPC integration keeps running until it fails. Once it fails, there is no path back to XML-RPC support — only a rebuild on REST v2.

What This Article Does Not Cover

This article covers the Thryv XML-RPC API deprecation date and where to find integrator help if you don't know who built your integration. This article does not cover the technical steps for rebuilding an integration on REST v2 — that guidance comes from the integrator you choose to work with, not from Thryv support.

If you already know who built your integration and want more detail on the deprecation date, what it means, and why to migrate now, see Keap XML-RPC API Deprecation: Updated Date and Migration to REST v2.

Comments

0 comments

Article is closed for comments.