@tommy yes this is still happening. I have compared the serialized request object and the only difference is the meetingid param. We have a hard coded bearer token is there something weird there where I don’t have access to see these meetings?
@tommy do you mean just for these meetings created with the testgcm site? This is not in line with what I am able to reproduce through the v2 apis as well as the workflow that we have been using on production for some time now. I am able to create a meeting with this api:
I enter the start url into a browser window to start the meeting and connect, then I call the get meeting endpoint and I get the meeting information returned to me without issue:
as you can see these meeting ids are the same and I made the call get meetings while I was connected to the meeting
I did some investigation and since the host of the meeting is Zoom, not your Zoom account, then you will not be able to access the meeting through the API.