It is pretty easy actually. See the following JSON returned with
/meetings/:meetingId?show_previous_occurrences=true ? I pasted only one occurrence record to keep it simple. If we had the meetingUuid which is corresponding to this meeting occurrence then it will be possible to get the registrants for that particular occurrence and also participants by using the meetingUuid from metrics or reports. I know it can’t happen before the occurrence / session but it is already necessary after the meeting - for past meetings.
Following solves this issue:
In fact, even adding registrants number into the occurrence array would be a more than great improvement.
About embedding occurrence array in the meeting list
Absolutely! This will reduce the API calls and the time that we pull info. Let’s say we have 100 meetings in a month and we try to retrieve occurrences for each meeting. In my current design, I have to get the list of meetings first (metrics/meetings?type=past&from=2020-07-01&to=2020-07-30&page_size=300) then for each meeting I have to get each meeting data separately (/meetings/:meetingId?show_previous_occurrences=true).
Instead, occurrences array could be embedded into the meeting array in the list of meetings API (again, with corresponding meeting UUID and registrant count). In my scenario above, it saves a lot of time and unnecessary processing of data.
Thanks again. How can I watch this possible improvements?