<@U034X65A6P2>, <@U032CMXGG4A> has the most contex...
# api
v
@Vikram, @Agusti has the most context here so he can confirm, but I believe these are the required request parameters for POST request to create a booking:
Copy code
{
    "title": "<title>",
    "uid": "<unique identifier>",
    "eventTypeId": <event type id>,
    "startTime": "2022-05-30T11:00:00.000Z",
    "endTime": "2022-05-30T12:00:00.000Z"
}
🙏 2
v
This worked thanks!
👍 2
not sure why but seems like you can actually double book as long as the event has a unique id....
z
👍 1
🙏 2
a
@Vikram yeah right now bookings are pure crud and not connected to availability, was gonna work next on that after landing availability in API
v
@Vikram yep, I ran into this as well -- being able to book slots that should be unavailable. I think @Agusti is working on a fix for this
ah, yep, @Agusti beat me to it 😄
🙏 1
v
This postman collection is super useful thanks. I think i somehow found a old collection
@Agusti anything we can do to help with the availability API?
a
Will be shipping today a first MVP @Vikram I think testing / giving feedback is a lot of help already. On the postman collection, might need some updating, let me know whatever you found there that looks outdate to update properly too, thank you 🙏
v
Sounds great! lmk when I can start playing around with it
v
thanks @Agusti! yep, excited to test it out as well 🙂
🙏 1
hi @Agusti, is the availability API ready to use in production?
👀 2