We are providing a closed captioning service and I am running into 403 errors trying to push captions into specific meetings. This doesn’t appear to be an issue for every meeting though. Specifically, testing the connection with a meeting on the same account on Friday worked as expected. It also doesn’t appear to be an OS issue, as described in this other thread (403 Errors posting to /closedcaption from Windows). The error happens consistently for this meeting on Windows and Linux.
Captions are enabled and the Token URL is being copy/pasted into our service.
For the given meeting, I also tried and failed to use /closedcaption/seq, which produces the same error, but that might be because of incorrect parameters, since that API call isn’t well defined in your docs and I just assumed the same auth params as for the POST call.
A call to
It would be incredibly helpful if the API would return an actual error message instead of an empty one, so it is possible to narrow down potential issues for developers.
Any help is greatly appreciated, thanks in advance!
// update: Testing it on my own account produces the same issue. Was there a change in the Captions API over the weekend?