Endpoint that uses cache when fetched frequently

This endpoint is improved version of v2/availability . If you are fetching availability for resource frequently without any change in the date range often then this might be a good endpoint for you.

How does it work?

When you request availability for your resource between some day range it would catch the response and next time you hit this endpoint you will get cached availability.

This way you can make more requests per seconds and get improved response time. Cache will be bursted in following scenarios:

  • When resource is updated with new constraints
  • When project is updated with new constraints
  • When new booking is created for specific resource


Cached TTL

This endpoint is cached for 1 minute of TTL. Cache will be bursted after a minute.

This endpoint will inherit your project settings if some params are not set as a payload.

Click Try It! to start a request and see the response here!