Have successfully used Rest PI V1 for several years between my cloud app (PICA) and keap. Stripe integrated w/ PICA so when user orders & pays, we pass contact id, product, qty, price, and create an order in keap, then pass /post payment made to keap. I then have records of order activity/history and keap emails invoice/sales receipt. . Used to work great - no muss, no fuss. BUT…I see there is nothing listed under Rest API V2 that allows me to create an order! I also see nothing in Products! Am I missing something? Am I spending lots more for Keap and getting less?
What you see is what you get. The REST API v2 has not been progressing, and no idea when it will be comparable to either REST v1 or the XML-RPC API.
Have you seen this recent discussion below?
Still no communication from Keap on what is going on with the API.
We have a huge chunk of new endpoints that are in Pre-Release and just waiting finally testing and verification. They should be coming out very soon. We also have made API our top priority for product in 2025 to get REST v2 to a state of value parity with XML/RPC and REST v1.
1 Like
@bradb
CC: @Marion_Dorsett2 @Pav
Thank you so much for sharing this update and for keeping us in the loop regarding the upcoming API developments. It’s great to hear that these new endpoints are in Pre-Release and close to final testing—it’s encouraging to see this progress.
That said, I feel it’s important to express that actions often speak louder than words. While we truly appreciate hearing about the intentions and priorities for the API, the journey to get to this point has been quite a long one, and tangible progress has often felt slow over the years. Seeing these new endpoints released and in action would provide far more reassurance than hearing about plans, however promising they may be.
We’re genuinely looking forward to seeing REST v2 evolve into a fully-featured and competitive solution, and we’re grateful for your focus on this critical part of the product. Thanks again for sharing these updates, and we’re excited to see the results of this work soon!
@bradb, thank you for the update.
Although the new endpoints will fill in some of the gaps, the main concern is the REST API querying capabilities. At the moment they are poor in comparison to the XML-RPC API. We need to see significant progress on that front so that developers can easily migrate to REST.
Also, several weeks ago Tom said there was no plans for the REST API to query the Custom Fields, due to a technicality. You need to address that blockage, because we can freely do that in the XML-RPC API without a problem.
I agree with @Timothy_Smith that we need to see progress happening in 2025.