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

**URL:** <https://devforum.zoom.us/t/bug-receiving-invalid-retry-after-header-from-zoom-api-when-trying-to-create-meeting/120665>\
**Category:** API and Webhooks\
**Tags:** api\
**Created:** [November 10, 2024, 5:15pm UTC](https://devforum.zoom.us/t/bug-receiving-invalid-retry-after-header-from-zoom-api-when-trying-to-create-meeting/120665 "2024-11-10T17:15:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elyes](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elyes/32/9007_2.png) [@elyes](https://devforum.zoom.us/u/elyes)\
**Post date:** [November 10, 2024, 5:15pm UTC](https://devforum.zoom.us/t/bug-receiving-invalid-retry-after-header-from-zoom-api-when-trying-to-create-meeting/120665/1 "2024-11-10T17:15:51Z")

</div>

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

[Create meeting endpoint](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/meetingCreate)

**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](https://datatracker.ietf.org/doc/html/rfc7231#section-7.1.3).

[An HTTP date is to be formatted like this](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Date#examples): `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](https://devforum.zoom.us/t/invalid-retry-after-header-on-create-registrant-api/57731), [2](https://devforum.zoom.us/t/invalid-retry-after-header/73804))

**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:

```auto
  {
  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.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [November 13, 2024, 8:59pm UTC](https://devforum.zoom.us/t/bug-receiving-invalid-retry-after-header-from-zoom-api-when-trying-to-create-meeting/120665/2 "2024-11-13T20:59:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 17, 2025, 12:35pm UTC](https://devforum.zoom.us/t/bug-receiving-invalid-retry-after-header-from-zoom-api-when-trying-to-create-meeting/120665/3 "2025-11-17T12:35:34Z")

</div>

Closed on November 17, 2025, 12:35pm UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.
