Let me say that some of us are not happy of what has occurred over the years with the API.
Timeline
Here is a timeline of things.
- 2006 (?) - XML-RPC API was initially released.
- 2015 - REST v1 went into design.
- 2016 - REST v1 was initially released.
- 2021 - REST v2 was initially released.
- 2025 July - Announcement of major expansion on REST v2.
- 2025 November - Announcement made that REST v2 was full feature parity.
- 2026 - REST v2 is still having ongoing development.
- 2026 December - End of life for XML-RPC API.
- 2027 (?) - Expected for REST v1 to be sunset (Next major API change).
@Christian_Wiles, if REST v2 was at the full feature parity, then I would 100% agree that a 1 year transition would have been plenty of time to do it. I think what happened is that when they made the announcement in July last year, whoever was in charge was either told or thought that there was enough functionality to match the XML-RPC.
There are parts of the REST v2 that Keap will not change which is not going to help developers, for example.
- Custom Fields Querying - No support to be added, unless you use a Saved Search which are a fixed search.
- Wildcard Support - Partially added, not the same as XML-RPC Wildcard support.
In the post link below, Keap will not change this endpoint. I have an integration that pulls a list of the Templates via the XML-RPC. I will not be able to do that in REST. This will require a change to the integration, making it awkward for the user to get the Email Template ID. Things like this add further development time which is not helpful.
https://integration.keap.com/t/rest-v2-email-list-email-templates/94087/2
The development of REST v2 is also being rushed, as inconsistencies are appearing, and not enough thought is being put into the endpoints. In XML-RPC all the monetary values appear as Decimal Numbers, which is helpful and consistent. On particular REST endpoints the team decided to add the related currency, which i can understand why, with the monetary values appearing as whole numbers as they want to make it flexible for different currencies. Not a problem just usually divide the amount by 100 to get the proper figure for that currency. But when going to other endpoints the monetary values are back to decimal numbers. If you have code relying on the original figures you will have to either divide or not divide the figures adding to further development work.
All of this trouble could have been avoided if the original team looked at the capabilities of XML-RPC and added that functionality into REST v1. Then the REST migration would have been done years ago, instead of taking 10 years.
Last week I raised several posts that were a combination of issues and requests. Now i need several of them to be resolved to be able to continue the migration. How long will it take for Keap to resolve them? Who knows, but that delays me further, and we only have 6 months to go. Some of us have other work to be getting on with and do not want to be dragged down by this migration.
Checking the Tracker today, there is now 12 gaps that are waiting to be reviewed, 5 are currently being tested, and 2 others are in progress. That does not include the recent gaps, other issues, and enhancements that have been raised either. That is going to take Keap several weeks to resolve those, and then it will be the end of summer.
Anyway, we all have different view points on this migration.