API Endpoint(s) and/or Zoom API Event(s)
Create a recording registrant /meetings/{meetingId}/recordings/registrants
Description
For meetings that have more than one recording, how do I specify which recording to create the registration for?
For example, in the portal I can see that meetingId99984966033 has two recordings. Through the API it only creates a registrant for one of them and not the other. How can I create registrations for the other?
Use the meeting UUID, not the numeric meeting ID, when you need to target a specific recording instance. Zoom’s Create recording registrant path takes meetingId, but that field can be either the numeric meeting ID or the meeting UUID.
For a recurring meeting or a reused meeting ID, first get the past instances and their UUIDs, then call Create recording registrant once per instance UUID that should get access. To confirm you have the right target, call Get meeting recordings with that same UUID and verify the returned recording_files match the recording shown in the portal.
For workflows that need to capture or retrieve meeting recordings across these kinds of edge cases, you can also look at Recall.ai’s Meeting Bot API.
Thanks, I discovered the same thing myself yesterday. Even though the documentation says meetingId must be int64, it also accept the UUID.