Hi @Agusti @zomars @Peer, I noticed the deletion of a booking (DELETE request to

<https://api.cal.com/v1/bookings/64628?apiKey=><key>

to delete booking id

64628

for example) is no longer working. PATCH to update (reschedule) booking does not work either. I am following the Postman collection . Did anything change with this? This is a crucial use case for us 🙏

cc @Agusti

Will check out and get back @Varun Krishnamurthy , dont remember any changes recently there

Thanks @Agusti . Please keep me posted, as our integration is ready for production once this is fixed :)

Hey @Varun Krishnamurthy, working right now on this hope to have it fixed in a couple hours, will ping you back here.

Thanks @Agusti! I am ready to test when it is ready 🙂

@Varun Krishnamurthy Do you know by any chance if the booking API accepts the email of the user and their guests to the booking API, to trigger booking confirmation email. Or is it something we need to handle with some separate service.

hi @Devan Thakur, that's a great question. based on the postman collection/API spec, it doesn't appear that the booking API accepts the email, but I could be wrong.

Ok. Thanks @Varun Krishnamurthy!

@Agusti @Ali @zomars Do you have an update on the ETA of the CRUD fixes for bookings (specifically, DELETE and PATCH to the bookings endpoint not working)? It is still broken. We are hoping to deploy our integration to production, but are currently unable to until this is fixed 🙏

Yes, we have been stuck with retrieve and cancel booking as well. We are just deciding to move to some other provider. The APIs don't seem to be stable enough.

yes, it is quite disappointing because I am big fan overall of what cal.com is working towards. But right now things with cal.com's hosted solution are very unstable -- I have lost confidence because this issue has taken almost 2 weeks (and counting) to resolve, and I was assured this would be investigated and fixed right after I reported it. it is core API functionality like retrieving, updating, and canceling a booking, which have been advertised on the website and postman documentation as working functionality. With that said, I would love to stick with the service if this issue can be resolved ASAP though

We're aware of the issue and it is high in our priorities. This two weeks have been very busy tackling some major and longstanding issues so API had to pass as second priority. But be sure that this is the next priority now

thanks for your message @zomars. Do you have an ETA on when the booking API functionality will be fixed in prod? I am hoping to communicate an accurate timeline to my team on when we can ship our integration 🙂

I'll prio this today and get back to you

Hello @Varun Krishnamurthy, we’ve correctly identified the problem recently and are right now working on the fix, expect an update soon when this works again (later today) will keep you posted! Sorry for the trouble and thanks for all your help and feedback!

Can confirm as well this has been fixed

thank you @Agusti and @zomars! testing now 🙂

Will take a look and get back at you