Something similar to the existing delete recordings API method. However, that method only accepts one conference ID to delete recordings for, and we need to delete conference data for many conferences at once. To be clear, we cannot simply delete the Iotum user. We need to delete some conferences for one or more Iotum users, based on a specific attendee. It's also worth mentioning that this is required for us as part of our TOS to limit liability for our customers.
I seems that this existing method could easily be expanded to allow an array of conference IDs instead of only one ID.
I also can't find an existing API method to delete a conference by ID. e.g. I can find nothing for `POST "/enterprise_api/conference/delete". So it looks like this would have to be added and, again, ideally would accept an array of conference IDs.
Describe alternatives you've considered
The only alternative is to iterate the conference IDs and call /enterprise_api/conference/delete_recordings one by one to delete them. But we have cases where we'll need to delete over 1000 conferences, so this will be very inefficient.
Something similar to the existing delete recordings API method. However, that method only accepts one conference ID to delete recordings for, and we need to delete conference data for many conferences at once. To be clear, we cannot simply delete the Iotum user. We need to delete some conferences for one or more Iotum users, based on a specific attendee. It's also worth mentioning that this is required for us as part of our TOS to limit liability for our customers.
I seems that this existing method could easily be expanded to allow an array of conference IDs instead of only one ID.
I also can't find an existing API method to delete a conference by ID. e.g. I can find nothing for `POST "/enterprise_api/conference/delete". So it looks like this would have to be added and, again, ideally would accept an array of conference IDs.
Describe alternatives you've considered
The only alternative is to iterate the conference IDs and call
/enterprise_api/conference/delete_recordingsone by one to delete them. But we have cases where we'll need to delete over 1000 conferences, so this will be very inefficient.