When making a call to the report meeting participants API, and when the meeting ID contains a “+” character, the API now expects that character to only be URL encoded once. While this does seem sane, previously (before 7/23 of this past month) these values needed to be double URL encoded (there are several topics on this in the forum).
I can find no API release notes regarding this change. Was this change intentional, and customers need to update their code? Or was it not intentional, and we should expect it to be fixed / rolled back?
Instead of receiving the participants, I get a “Error: No participants found”, and the API now interprets the double encoded “+” as a space character. Previously this value needed to be double URL encoded.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
The report meeting participants API
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Make a request to the above endpoint with a meeting ID that has a “+” character in it. Only URL encode the character once. See that it returns results. URL encode it twice, then verify it does not return results.
I use this endpoint: https://api.zoomgov.com/v2/