@OmarAlmonte and others,
As I seek to better understand the current state of the Keap API, it would be helpful to know whether the REST hooks documented in Keap’s REST v1 will continue to be supported in the future: Rest Hook Documentation - Keap Developer Portal
It is clear that XML-RPC will be going away later this year, but will REST v1 be sticking around for a while until features (like REST hooks) are supported in later versions?
Please let me know if you need clarification regarding what is being asked.
Thanks,
Tim
Hi @Timothy_Smith,
Regarding the REST hooks, yes, an upgraded version will be available in v2. I’ll share more details as soon as I can.
If you run into anything that exists in v1 but isn’t available in v2, please bring it to my attention and I’ll raise it internally.
Thanks for checking in, happy to help.
Upgraded?
Just a version bump, copied straight from v1 to v2?
Or, will they carry payload data?
Or, will there be some kind of batching planned?
Or is there some other aspect that will be upgraded from the v1?
Not looking for a super detailed commitment, just a rough sketch of what’s planned, so we can work them into our plans (or not).
1 Like
@David_Bullock, this is being discussed, I’ll share more as soon as I can.
2 Likes
@OmarAlmonte if we could have what was updated with a REST hook, that would be awesome! The current process is Keap says something is updated by providing the Contact ID. We then need to investigate and compare to what we have cached in order to tell what changed. If we knew which field/property changed and even who changed it (user ID) and when (date/time), that could be super valuable!
Thank you for the feedback! I’ll be sure to bring this up in our internal conversations.
1 Like