Easier way to get events via API

right now im trying to find an event_type thats not under the user or the “current_organization” i got from running api for user details

but its in the back of his calendly….

so im just lost and annoyed

@sell63550 Currently, the scope and authentication method of our APIs are tied to the User or the Admin/Owner of that Org. When you authenticate our APIs using token belonging to the either User or Admin/Owner, you will get Event Types specific to the scope of that token. For security reasons, you will not be able to retrieve data from a different Calendly Org unless you are a part of that Org and use their token.

Can you share your use case? We can provide additional help on how to proceed. 

sell63550

if you are a pro user then you can easily track your users information (like first name, last name, email, phone and others) for your Facebook and Google Marketing and I know how to track them by using Google Tag Manager (GTM)

Totally valid frustration and this is a really common pain point with API design where chained identifier lookups create unnecessary complexity that slows down developer workflows significantly. The quickest practical workaround is to run a one time API call to fetch and locally store all your event type IDs in a simple JSON reference file so your team is not repeatedly hunting for identifiers, and ideally the platform should surface these IDs directly in the frontend URL structure or at minimum in the event settings page so developers can grab them instantly without any API calls at all.

Really agree with this, the nested API lookup pattern where you need an ID to get an ID to get another ID is one of those developer experience bottlenecks that seems minor on paper but genuinely adds up to hours of lost productivity over time especially when you are onboarding new team members who have no existing reference of what identifiers map to what objects in the system. Displaying the unique identifier directly in the frontend URL or in a dedicated developer info section within each event settings page would be such a low effort high impact improvement that would immediately reduce support requests and API confusion across the entire developer community using this platform.