Here is what I did: I scheduled a recurring meeting (type 8) with 3 occurences. The meeting is ‘live’, i.e. ongoing. Using the API I get the ‘upcoming’ and ‘live’ meetings.
Requesting the ‘upcoming’ meetings all three scheduled meeting occurrences are returned as expected. Requesting ‘live’ meetings, only one meeting occurrence is returned. However, the start_time of this occurrence is the start_time of the last of the scheduled occurrences, NOT the start time of the currently ongoing meeting.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
thanks a lot for the clarification. I agree that this “feature” is quite a bit confusion, since requesting “upcoming” meetings does return all (live and future) occurrences. So, one would expect the “live” query to return occurrences that are ongoing. Maybe this should be documented somewhere?
In either way, I don’t see how the strategy you describe will provide me with the occurrenceID of the meeting that is live? How would I know which of the occurrences is the live one? The status string always seems to have the value available. No matter if the meeting is ongoing or not…