I hope this message finds you well. I’ve been actively using the Keap API and truly appreciate the functionality it provides for integrating with various tools. However, I noticed that the API does not appear to have been updated in a while. Several functions must be done in XML-RPC, which is supposedly going to be deprecated at some point.
I was wondering if there is a roadmap or any communication channel where updates or planned new features for the API are announced? Having visibility into this would be incredibly helpful for planning and optimizing integrations.
One specific example of something that would be helpful is the ability to create and update Deal records (Not Opportunity Records) in Keap’s Pipeline.
Thank you for your time, and I look forward to any insights you can share.
Let me say the following, the API is in an absolute mess now-a-days. There is no communication about things, no Roadmap you can see, lack of progress, not listening to the community, and usually very little official response when anyone ask questions about it.
As far as I know the API started its life in 2006 under the XML-RPC API. That progress quite well over the years until the company decided it was no longer suitable for future expansion. In the latter part of 2016 the REST API was introduced with new Endpoints slowly being added. You would see people several years ago saying that XML-RPC would be deprecated in favour of the REST API. That is understandable progress needs to be made, and we would have to make the changes to do so. In a perfect world, or in other words, people who know what they are doing, we should all be using the REST API by now.
Unfortunately, bad decisions have been made along the way. The REST API v1 was not comparable with the XML-RPC API, as it misses several pieces of functionality. To address that issue the company decided to work on REST API v2 to overcome the shortfalls. But from what we are seeing, it is still not comparable with the XML-RPC API. The REST API Querying capabilities are awful and are not matching the XML-RPC API. In a recent discussion the company mentioned they will not offer the ability to search Custom Fields because they are not Indexed.
What has happened is now we have integrations that are either using the XML-RPC, or REST v1, or REST v2, or combinations of them.
Here is a recent example of someone asking a REST API question 3 years ago, and still no official response to it. You have to use the XML-RPC to do that task.
The only thing I know that is coming is that the PIpeline API being developed which was recently mentioned in this post.
Who knows what is going to happen in the future. Maybe by the year 2030 the REST API v2 will be completed!
@Timothy_Smith In addition I found a bug in the REST V1 API that won’t be fixed because it’s been resolved in REST V2. So that being said, make sure you always use the REST V2 endpoint, unless it doesn’t exist.
I’ll stick to the XML-RPC until the REST can do what my clients need. The RESTHooks can be useful so you don’t have to poll for data, but the lack of parity between the APIs presents a bigger issue when trying to compare citrus to non-citrus plants.