Issue with Zoom API Registrations Not Reflecting in Zoom Accounts

How To
1

Hello Makers friends,

I’m experiencing an issue with the Zoom API when attempting to register participants for meetings. Despite receiving confirmation emails and responses from the API that suggest the registrations were successful, the registrants do not appear in the Zoom account associated with the meetings. Here’s a detailed breakdown of the problem:

Context:

  1. API Used: We’re using the Zoom API with the Server-to-Server OAuth application type.
  2. Scope: Full permissions are granted, including viewing and managing meetings and participants.
  3. Process:
  • We send a POST request to the Zoom API endpoint /meetings/{meetingId}/registrants.
  • The response from the API includes a registrant_id and a confirmation message.

Problem:

  • Although the API returns a success response and sends confirmation emails to the registrants, these registrations do not appear in the Zoom account under the meeting participants list. The registrants also do not see the meetings in their Zoom accounts.

Troubleshooting Steps Taken:

  1. Verified API Scopes: Confirmed that all necessary permissions are enabled.
  2. Checked API Responses: The responses indicate successful registrations (status: 201 Created).
  3. Double-Checked Meeting Settings: Ensured that registration is required for meetings.
  4. Tested with Different Meetings: Tried registering participants in both new and existing meetings with the same result.
  5. Validated Participant Accounts: Verified that the participant emails used have valid Zoom accounts.

Additional Information:

  • No errors are returned from the API that suggest a problem with the request.
  • This issue has been tested with multiple emails and meetings, all resulting in the same outcome.
  • We have tested the process both using Make.com and direct API calls, with the same results.

I’m not a developer, and we’re trying to automate this process because our number of students has increased, making manual registration no longer viable. Any insights into what might be going wrong? Are there any known issues with the API that could be causing this behavior? Any advice on additional steps we should take to debug or resolve this issue would be greatly appreciated.

Thank you in advance for your assistance.

CARLOS

2

How did you manage the Redirect URL for OAuth with an S2S Server-to-Server OAuth app?

this is the redirect URL we need to use
https://www.integromat.com/oauth/cb/zoom2