As many of you have become aware, we have officially announced to our customers and our registered integrators that we are sunsetting XLMRPC effective December 31, 2026. We understand change is always met with trepidation, even in the rapidly changing technology world, so we are providing a full 13 months to complete this migration. In an effort to help make this transition as smooth and manageable as possible, we’ve created extensive documentation to guide you through the migration from XML-RPC to REST v2, providing step-by-step instructions, technical references, and resources designed to support you every step of the way:
For any technical questions about this process, reach out to our API specialist, Omar Almonte, by posting in the Developer Forum(API Q&A - Keap Integration Q&A).
The email is being sent to Keap app owners who have had recent XML-RPC traffic. At this time, the sunset date has not changed. If anything does change, we’ll be sure to communicate updates through our channels.
But what if your team spend the next 3 months trying to implement all the gaps? As developers migrate their code across, I would expect further gaps to be discovered.
The problem I have got is that i cannot continue migrating all the code across until you have finished completing some of the gaps. That means I am delayed and with the December timeline getting closer I will have less time to migrate across.
I would like to clarify the emails I have received are Partner-specific emails and not an app-specific emails. Here is the most recent example:
Hi Timothy,
We hope things are going well! As part of our ongoing commitment to keeping you informed, here’s your monthly reminder about the upcoming XMLRPC sunset and what it means for you.
XMLRPC Is Being Retired on December 31, 2027
On December 31, 2027, support for XMLRPC will officially end. After this date, any integrations or tools that rely on XMLRPC to connect with Thryv will no longer function. The good news — you have time to prepare, and we’re here to help every step of the way.
What This Means for You
If you use any third-party tools or custom integrations, they may be using XMLRPC without you knowing it.
After the sunset date, those connections will stop working if they haven’t been migrated.
Now is a great time to connect with your vendors or developers to confirm whether action is needed.
How to Use Your Time Wisely
We strongly encourage you to start preparing now. Here’s where to begin:
Identify XMLRPC usage: Audit your applications and integrations to determine what’s using XMLRPC.
Review the migration guide: Understand what’s involved in moving to our current REST API.
Plan your migration strategy: Determine the timelines and resources you’ll need.
Take advantage of available resources: Access documentation, SDKs, and community support.
We’ll continue sending these monthly reminders to keep the sunset top of mind. As we get closer to the deadline, we’ll share more detailed guidance and any updates to the timeline.
Please note: The December 31, 2027 sunset deadline is firm. We encourage you not to wait — starting your migration planning early will ensure a smooth transition with no disruptions to your business.
Thank you for your continued partnership. As always, our support team is here if you have any questions!
@OmarAlmonte already confirmed the date in the email is wrong.
I am a Partner User on several Keap accounts and have not been receiving notifications about XML-RPC from anywhere except from partners@keap.com. It’s possible none of the XML-RPC traffic is considered recent enough, but I am only receiving emails because I am a partner - not because of XML-RPC traffic. This may be something to double-check to ensure your metrics for identifying XML-RPC usage is accurate. I cannot say for sure whether my accounts are sending XML-RPC traffic, but it sounds like @Jeffrey_Chimene may need you to take a closer look at at least one app.
@OmarAlmonte, I need to raise some points regarding this email.
Deadline - Is December 31, 2027 the new deadline date? Whoever wrote the email must have been informed about the deadline, because it is mentioned several times with the 2027 year now. Your team still have several weeks of work to fill in the outstanding gaps, and there will be additional ones coming in the future.
App Owners - Do not assume that all application owners will be informed. Granted that the majority will receive and understood it. But I have come across people in the past where the owner is not always getting the emails which is due to either non-functional email addresses, or they have a technical team handling the account. What you should be doing is to email all the Administrators of the account, then you would get someone attention.
Brownouts - What happens when the Brownouts start to occur again in the future? How will the owners get notified? When are you predicting you will be starting the brownouts again?
Thank you for the thoughtful feedback and for raising these concerns.
As mentioned previously, at this time nothing has changed regarding the current timeline or plans. We also do not have a timeline for brownouts right now. That said, we will make sure to post and communicate any updates or changes as soon as we have them available.
We also appreciate the suggestion about notifying all application administrators, that’s valuable feedback for the team.
Thanks again for taking the time to share your concerns.
