So you are following Calendly’s dev docs and trying to paginate through the scheduled_events collection.
Then you get a cryptic “page_token is invalid” error. You check Bubble’s logs and of course they are useless. You check your browser logs and also useless.
You try an API call with Bubble using the full next_page value returned and it works. But of course that’s useless in Bubble because then you have two API calls returning identical but different data in the Bubble world.
You Google around and someone has encountered this error:
On your first call to the endpoint, Calendly accepts a date format without milliseconds. But subsequent calls to the same endpoint with the same parameters plus page_token breaks.
For some reason, Calendly demands milliseconds in subsequent calls with the page_token parameter. So make sure that you are including milliseconds if you are using the min_start_time or any timestamp parameters with Calendly!!
Dropping it here to make this solution easier to find when someone is fighting with the same issue.
Also farming some sweet likes…hint
Okay fine, service is its own reward.