# REST API to get available time-slots & book an appointment

**URL:** <https://forum.youcanbook.me/t/rest-api-to-get-available-time-slots-book-an-appointment/660>\
**Category:** API\
**Created:** [February 28, 2020, 8:44am UTC](https://forum.youcanbook.me/t/rest-api-to-get-available-time-slots-book-an-appointment/660 "2020-02-28T08:44:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neel](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@Neel](https://forum.youcanbook.me/u/Neel)\
**Post date:** [February 28, 2020, 8:44am UTC](https://forum.youcanbook.me/t/rest-api-to-get-available-time-slots-book-an-appointment/660/1 "2020-02-28T08:44:51Z")

</div>

Hello there,

I would like to integrate [Youcanbook.me](http://Youcanbook.me) with Google Dialogflow (webhook call) to book an appointment via REST API.

I’m looking for the following functionality

1. Get available time-slots from the given date range (Feb-28-2020 to Feb-29-2020)
2. Book an appointment

Does [YouCanBook.me](http://YouCanBook.me) has support above functionality via API?

---

<div class="post-metadata">

**Author:** ![Ben](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.youcanbook.me/ben/32/772_2.png) [@Ben](https://forum.youcanbook.me/u/Ben)\
**Post date:** [March 3, 2020, 6:36pm UTC](https://forum.youcanbook.me/t/rest-api-to-get-available-time-slots-book-an-appointment/660/2 "2020-03-03T18:36:26Z")

</div>

We do not have a public availability end point. You would need to use Google Calendar API to request this, then pass in the information via our API for the booking date and time to book.

---

<div class="post-metadata">

**Author:** ![Jeremie](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.youcanbook.me/jeremie/32/267_2.png) [@Jeremie](https://forum.youcanbook.me/u/Jeremie)\
**Post date:** [March 31, 2020, 8:23pm UTC](https://forum.youcanbook.me/t/rest-api-to-get-available-time-slots-book-an-appointment/660/3 "2020-03-31T20:23:18Z")

</div>

@Ben YCBM has a wonderful API, but I think this is an oversight. I would encourage you to expose the necessary model. I think it makes your API more sticky, because ass you mention yourself, this completely removes the need to use any other API from other calendars. In a sense, if you allow for exporting of availabilities, you are an aggregator for calendars.