# Issue with HubSpot Scheduler API: Incomplete Availability Data

**URL:** <https://community.hubspot.com/t/issue-with-hubspot-scheduler-api-incomplete-availability-data/140254>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [September 29, 2025, 11:40am UTC](https://community.hubspot.com/t/issue-with-hubspot-scheduler-api-incomplete-availability-data/140254 "2025-09-29T11:40:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MSygkelakis](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@MSygkelakis](https://community.hubspot.com/u/MSygkelakis)\
**Post date:** [September 29, 2025, 11:40am UTC](https://community.hubspot.com/t/issue-with-hubspot-scheduler-api-incomplete-availability-data/140254/1 "2025-09-29T11:40:11Z")

</div>

### Issue with HubSpot Scheduler API: Incomplete Availability Data

I’m trying to use the HubSpot Scheduler API endpoint:

`https://api.hubapi.com/scheduler/v3/meetings/meeting-links/book/availability-page/{slug}?timezone=Europe%2FAmsterdam`

I receive a response from the API that is mostly correct, but it only includes available slots for the next two days. In the response, there is a property called hasMore which is true, but there are no options provided to retrieve the additional dates.

I’ve tried using query parameters like offset and page, but they don’t seem to work.

Has anyone encountered this issue or knows the correct way to retrieve all available slots beyond the initial days?

---

<div class="post-metadata">

**Author:** ![BrandonWoodruff](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/brandonwoodruff/32/61045_2.png) [@BrandonWoodruff](https://community.hubspot.com/u/BrandonWoodruff)\
**Post date:** [September 29, 2025, 2:15pm UTC](https://community.hubspot.com/t/issue-with-hubspot-scheduler-api-incomplete-availability-data/140254/2 "2025-09-29T14:15:14Z")

</div>

To retrieve all available time slots, you need to make additional API calls with an incrementing monthOffset value. The initial call without this parameter only returns the availability for the current month.

Here’s how to get the October availability:

1. **Your initial request:** GET /scheduler/v3/meetings/meeting-links/book/availability-page/slug?timezone=Europe/London This request correctly returns the availability for September.
2. **To get October availability, add &monthOffset=1 to your request:** GET /scheduler/v3/meetings/meeting-links/book/availability-page/slug?timezone=Europe/London&monthOffset=1

By including monthOffset=1, the API will return the availability for the next month.

This solution is also found in: [https://community.hubspot.com/t5/APIs-Integrations/Scheduler-v3-API-only-returns-2-days-despite-UI-showing-more/m-p/1205526#M84607](https://community.hubspot.com/t5/APIs-Integrations/Scheduler-v3-API-only-returns-2-days-despite-UI-showing-more/m-p/1205526#M84607)

Let me know if this helps, or if you have any other questions!

* * *

✔ Was I able to help answer your question? Help the community by **marking it as a solution.**

| ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/3/d314478a36473977ed45320812b9331d25e0d3c4.jpeg) | **[Brandon Woodruff](https://www.linkedin.com/in/brandon-woody-woodruff/)**  
Senior Software Developer @ [Pearagon](https://www.pearagon.com/)Still have questions? Reach out at [brandon@pearagon.com](mailto:brandon@pearagon.com) ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/c/dcad77e6cf96145dd117147531ae4423b9b5cd91.png) |

* * *