Skip to main content
Kat80636
Community Member
July 1, 2025
Question

What is the UUID referenced in the API for scheduled_events?

  • July 1, 2025
  • 16 replies
  • 1051 views

I want to get a list of all of the people outside of our organization who have attended our events. If I do this:


curl --request GET \
  --url "https://api.calendly.com/event_types?organization=https://api.calendly.com/organizations/" \
  --header 'Authorization: Bearer {hidden} \
  --header 'Content-Type: application/json'

 

Then I seem to get a list of all of the events, but the list is much shorter than it should be. 

How do I get a list of every event that we’ve done in the last 6 months? 

Once I have that, I would like to get a list of attendees. So I try this:


curl --request GET \
  --url "https://api.calendly.com/scheduled_events/3df748e3-6d1a-4ede-abcd-39b1de2c17ca/invitees?organization=https://api.calendly.com/organizations/" \
  --header 'Authorization: Bearer {hidden} \
  --header 'Content-Type: application/json'

 

I’m using a UUID I found in the responses to the first cURL call that I did above. But that does not work. I get “Resource not found.” 

 

So what am I supposed to use for that UUID? Where would I find the UUID?

 

If I go here:

https://developer.calendly.com/api-docs/2d5ed9bbd2952-list-events

The page never mentions a UUID. I cannot find a reference to the UUID anywhere in any of the descriptive text, and yet it is listed as a required parameter when asking for the invitees.

 

 

    16 replies

    Show previous replies
    Kat80636Author
    Community Member
    July 10, 2025

    Does anyone answer these questions? Is there another source of support? Should I report this as a bug? Why is the UUID missing?

    Kat80636Author
    Community Member
    July 11, 2025

    Does anyone know anything about the field called UUID?

    Global20257
    New Community Member
    July 11, 2025

    You're querying the /event_types endpoint, which returns event templates, not scheduled events. To get all events that actually occurred in the last 6 months, you’ll want to use the /scheduled_events endpoint instead, and apply a min_start_time and max_start_time filter in your query.

    Once you have the event UUIDs from there, you can call /scheduled_events/{uuid}/invitees to get the list of attendees for each

    James81872
    New Community Member
    July 12, 2025

    Thanks for the info!!

    Christopher62888
    New Community Member
    August 4, 2025
    Kat80636 I think I see your issue. It’s the issue I was having anyway.

    In order to get the UUID, you have to first get the user or organization UUID.

    Calendly states: 
     
    Instead of referencing unique resources by an ID, which can be common in some RESTful APIs, we've decided that a more uniform approach to identifying a resource is to use a Uniform Resource Identifier (URI).
     
     
     

    So first, we get the URI from ourselves as admin. If you run [ https://api.calendly.com/users/me ], being sure to pass in your bearer token, you should get back a response with your details.
     
    {

      "resource": {

        "uri": "https://api.calendly.com/users/AAAAAAAAAAAAAAAA",

        "name": "John Doe",

        "slug": "acmesales",

        "email": "user@example.com",

        "scheduling_url": "https://calendly.com/acmesales",

        "timezone": "America/New York",

        "time_notation": "12h",

        "avatar_url": "https://01234567890.cloudfront.net/uploads/user/avatar/0123456/a1b2c3d4.png",

        "created_at": "2019-01-02T03:04:05.678123Z",

        "updated_at": "2019-08-07T06:05:04.321123Z",

        "current_organization": "https://api.calendly.com/organizations/AAAAAAAAAAAAAAAA",

        "resource_type": "User",

        "locale": "en"

      }

    }

    The end points of the URIs are your UUIDs.

     

    https://api.calendly.com/users/ABC123XYZ789UUID=ABC123XYZ789
    https://api.calendly.com/organizations/ABC123XYZ789UUID=ABC123XYZ789


    You’ll either use the UUID from the user or the organization, depending on the use case.

    I hope that helps! :)

     
      Christopher62888
      New Community Member
      August 4, 2025

      Quick fix on my last post, the entire URI is the UUID.

      Terms & ConditionsAccessibility statement