API sunsets · Thryv · checked 8 Oct 2026

Keap XML-RPC API (Thryv) shutdown on 31 December 2026

Keap XML-RPC API (Thryv) shuts down on 31 December 2026. After it, every XML-RPC call stops working; and a few XML-RPC methods have no REST v2 equivalent. The failure is loud: calls return errors. Thryv names REST v2 as the replacement (https://api.infusionsoft.com/crm/rest/v2/, with OAuth 2.0 in place of legacy keys). Record your real calls on XML-RPC before the date and replay them on REST v2: after it, nobody can record what XML-RPC returned. Find every place your code pins XML-RPC: npx --allow-git=root github:agentwares/api-sunset scan

$ npx --allow-git=root github:agentwares/api-sunset scan

npx --allow-git=root github:agentwares/api-sunset scan lists every API version your code and config pin (Shopify, Meta Graph, Google Ads, HubSpot, Stripe and the rest of this list) with its end date, what breaks and this page's link. It needs no account and no API key, reads your files on your machine and sends nothing; its one request fetches this data. Free and MIT licensed.

The facts

API: Keap APICovers the XML-RPC endpoint, api.infusionsoft.com/crm/xmlrpc.
Version: xml-rpc
Ends: 31 December 2026
After the date: calls fail
Silent?: No: calls return errors
Replacement: REST v2https://api.infusionsoft.com/crm/rest/v2/, with OAuth 2.0 in place of legacy keys

What breaks after 31 Dec 2026

All XMLRPC endpoints, including the ones not being converted to REST v2, will stop working on December 31, 2026. Any integration that has not migrated to REST v2 or an approved alternative will experience API failures. source
A small number of XMLRPC endpoints will not be directly converted to REST v2; Thryv's Gap Analysis Justifications spreadsheet lists each one with recommended alternatives. source

Keap is Thryv's; its XML-RPC endpoint is https://api.infusionsoft.com/crm/xmlrpc.
Thryv's help pages refuse automated readers; this entry was read through the same help centre's article API on 8 October 2026 (article last edited 23 June 2026).

How to upgrade

Find every place your code and config pin XML-RPC: npx --allow-git=root github:agentwares/api-sunset scan prints each file and line, and the variable name for a .env file, never its value.
Read what changed between XML-RPC and REST v2 in Thryv's notes, and list the calls that touch it.
Before 31 December 2026, send your real calls to XML-RPC and to REST v2 and compare the answers: same status, same fields, same values where they should match; after it, nobody can record what XML-RPC returned.
Change the version string, deploy, and watch the first day's responses.

Record your real calls on the old version before the date, and replay them on the new one.

agentcheck runs scheduled checks of an endpoint. A check sends the request you define (a path or a full URL, a method and a body, with your API key as a header, stored encrypted) on a schedule and compares each response with a golden: exact text, contains, a regular expression or a JSON Schema, none of which costs an LLM call. When a response stops matching, it opens an incident and alerts you. Point one check at XML-RPC and one at REST v2 with the same golden, and you see which of your calls answer differently before 31 December 2026.

Free: 1 monitored target, hourly checks, badge and public status page. Starter: 3 targets, 5-minute checks, Slack and Discord alerts, 30-day history. Recording the calls your code already makes is a different path: the trace import (POST /api/v1/targets/{id}/traces, or the agentcheck_record MCP tool) takes agent traces, a prompt and an answer, and turns them into checks judged by the LLM judge (Pro). It does not take raw HTTP requests and responses, so for an API the scheduled checks are the way in today.

Migration watch is not built. It would record the calls your code makes to Keap XML-RPC API (Thryv) and replay them on REST v2 until 31 December 2026, with nothing to set up, and email you what answers differently. If you would pay for that, say so with one click. The click is counted; nothing else is sent or stored.

Sources

XMLRPC Endpoints Not Being Converted to REST v2: What Developers Need to Know — the date and the replacement, read 8 Oct 2026

Built only from Thryv's own pages. No intent is implied: a date is what the page says on the day it was read. Data: /apis/sunsets.json.

api-sunset is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes.