/users/{userId}/meetings - use languages for language interpretation

Feature Requests
1

Change the meetings API (https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) so that languages can be specified for language interpretation, not countries, using internationally recognised language codes.

I’m frustrated because on the UI I can specify any language I want. On the API I have to specify a country code from a limited list, which does not make sense.

API Settings specfication

image
image1254×144 20.2 KB

Zoom App UI:

image
image592×611 19.2 KB

Zoom Admin UI:

Screenshot 2021-08-23 062239
Screenshot 2021-08-23 0622391291×265 23.9 KB

On the UI I can use languages and specify any language I want. Using Country codes on the API does not make sense. In the Unitied Kingdom of Great Britain and Northern Ireland (Country code GB) we have 14 indiginous languages - see Languages of the United Kingdom - Wikipedia. So which of those languages is being specified by the country code “GB”? On the API I get an error when specifying ‘GB’, to get English I have to specify “US” (a little offensive given where English originates from).

Describe the solution you’d like
Do not restrict the language to a limited list of countries. Allow a free form language description eg (“English,Swahili”) or a language code (eg (“en,sw”) or a mix of the two.

Zoom should use the ISO standard lists not imposing their own (see List of ISO 639-1 codes - Wikipedia.

Describe alternatives you’ve considered
Allow access to the list of languages specified in the Zoom Admin UI, included those that are added that do not exist in Zooms restrictive list.

Please see Language Interpretation error 400 for additional context.

1 Like
2

@matt_b Thank you for submitting this, I’ve reached out to our team to have this request considered for a future release. (ZOOM-302925)

1 Like
3

Are there any updates on this? It’s a huge miss that Language interpretation cannot be specified properly in the API.

4

Hi, any progress on this please?

5

Hi, has this moved forward yet? Lack of parity between the API and the admin UI is still a setback for us.

6

Very disappointed that there is no response on this. If we take time to submit a feature request and update on progress or confirmation that it is not going to be taken forward would be apreciated.

7

Still no progress or response?

8

Hi, I see you still have completely modelled this wrong on Country, not Language for interpretation. Please make the changes needed in the API for this to work properly (like it does in the real world where I would interpret someone’s language, not their country!)