Bug: receiving invalid retry-after header from Zoom API when trying to create meeting

API Endpoint(s) and/or Zoom API Event(s)

Create meeting endpoint

Description

We are receiving a Retry-After header from the Zoom API create meeting endpoint that is in an invalid format. This is causing our request handling library to crash.

According to the IETF, a Retry-After header can either be an HTTP Date or a number of seconds.

An HTTP date is to be formatted like this: Wed, 21 Oct 2015 07:28:00 GMT but we are receiving it from the Zoom API in the following format: 2024-11-09T00:00:00Z which appears to be an ISO format.

Our request handling library crashes when trying to parse this header.

It looks like this issue has occured previously in the Zoom API but is recurring for us (1, 2)

How To Reproduce

Steps to reproduce the behavior:

1. Request URL / Headers (without credentials or sensitive info like emails, uuid, etc.) / Body

METHOD: POST

URL: https://api.zoom.us/v2/users/<email>/meetings

BODY:

  {
  duration: 30.0,
  password: <redacted>,
  settings: {
      join_before_host: True,
      use_pmi: False
  },
  start_time: "2024-11-20T21:30:00Z",
  topic: "<redacted>",
  type: 2
  }

2. Authentication method or app type

OAuth - Admin-level app

3. Any errors

It’s likely that we’re receiving an error response because the Retry-After header is being included, but the actual error code / message is masked by our request library crashing when trying to parse the header. I will try to add logging to get around this and update the question if I can determine the response details.

Hi @elyes
Thanks for reaching out to us!
Would you be able to share with me all the headers you are getting so I can take a closer look to this please, if you have them let me know so I can DM you