What parameters are needed to fetch appointment list from Calendly API?

Other Questions Calendly
1

I’m trying to retrieve booked appointments through the Calendly REST API but getting errors with the organization parameter.

First, I call the user info endpoint:

https://api.calendly.com/users/me

This returns my user details and current_organization URI. Then I try to fetch appointments using:

https://api.calendly.com/scheduled_events?organization=abc123def-4567-8901-b2c3-456789abcdef

I’m passing the organization ID from the previous response, but I keep getting “invalid organization” errors. I don’t want to use webhooks for this. What’s the correct way to format the organization or user parameter when calling the scheduled events endpoint? Am I missing something in how I extract the organization identifier from the user profile response?

2

You’re passing just the organization UUID instead of the full URI path. When you grab the current_organization from your user profile response, use that entire URI string in your scheduled_events request. The organization parameter needs the complete URI format: https://api.calendly.com/organizations/your-uuid-here. But here’s a better approach - try using the user parameter with your user URI instead. I’ve found this way more reliable for fetching personal appointments. The endpoint becomes https://api.calendly.com/scheduled_events?user=https://api.calendly.com/users/your-user-id. Also double-check your authentication headers have the Bearer token formatted correctly. I’ve seen those “invalid organization” errors that were actually auth issues, not parameter problems.

3

Been there with Calendly API headaches. The parameter format’s tricky but you’re close.

Use the full organization URI, not just the ID. So instead of organization=abc123def-4567-8901-b2c3-456789abcdef, do organization=https://api.calendly.com/organizations/abc123def-4567-8901-b2c3-456789abcdef.

Double-check your headers have the auth token and content type.

Manual API debugging gets old fast though. I automated my whole Calendly workflow with Latenode - it handles parameter formatting automatically and I can pull appointments, sync with other tools, and set up triggers without code.

Saved me hours of debugging. Worth checking out if you’re doing more than one-offs.

4

hey, totally get where ur coming from! i had issues with this too. just make sure to use the full URI for the organization, like https://api.calendly.com/organizations/abc123def-4567-8901-b2c3-456789abcdef. that should sort the error out!