Unable to retrieve past meeting instances and survey reports for newly added user in same Zoom account

API and Webhooks
1

Hi Zoom Community,

I’m using the Zoom REST API with a Server-to-Server OAuth app to retrieve:

  • Past meeting instances
    GET /v2/past_meetings/{meetingUUID}/instances

  • Post-meeting survey results
    GET /v2/report/meetings/{meetingUUID}/survey

This setup has been working reliably for about 3 months.

Current setup

  • All meetings belong to one Zoom account

  • There are 4 users in this account

  • All users have admin roles

  • The same S2S OAuth app and access token are used for all API calls

  • Access token works correctly for the first 3 users

Problem

Recently, I added a 4th user to the same Zoom account.

For this new user:

  • Meetings exist and run normally in the Zoom UI

  • However, API calls such as:

    GET /v2/past_meetings/{meetingUUID}/instances
GET /v2/report/meetings/{meetingUUID}/survey

    return empty results or errors, while the same calls work for meetings hosted by the other 3 users.

The access token is valid.

Question

Is there any additional configuration required when adding a new user to an existing Zoom account so that:

  • Their hosted meetings are accessible via the Past Meetings and Report APIs?

  • Or any licensing, role, host ownership, or activation step that is required for new users to appear in API results?

Since this works for the other users with the same app and token, I want to understand:

  • Whether new users must be explicitly activated for reporting APIs

  • Or if certain meeting types (non-recurring, license limitations, host ownership) can prevent past_meetings and report endpoints from returning data

Any guidance on what needs to be checked or configured would be greatly appreciated.

Thank you!

2

hi @Luca1 ,

is this authorisation by Group?
What is you authorise the app for that new user individually.

John

3

Hi @Luca1,

This is a known behavior with Zoom reporting APIs when a new user is added.

A few things to double-check:

• Make sure the new user is fully activated (not just invited) and has logged in at least once.
• Confirm the user has a Licensed host role — reporting endpoints often return empty data for Basic users.
• If your S2S OAuth app is authorized at the account level, verify that the new user is included in the same account and not restricted by group-level permissions.
• Also check that the meetings are actually completed and not still in progress or recently ended (reports can take some time to populate).

In some cases, regenerating the access token after adding the user also helps ensure permissions are refreshed.

Hope this helps clarify.