# Zoom API returns DynamoDB Throttling Error on Meeting Creation

**URL:** <https://devforum.zoom.us/t/zoom-api-returns-dynamodb-throttling-error-on-meeting-creation/132024>\
**Category:** Meetings\
**Tags:** api\
**Created:** [April 28, 2025, 2:48am UTC](https://devforum.zoom.us/t/zoom-api-returns-dynamodb-throttling-error-on-meeting-creation/132024 "2025-04-28T02:48:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ark](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@ark](https://devforum.zoom.us/u/ark)\
**Post date:** [April 28, 2025, 2:48am UTC](https://devforum.zoom.us/t/zoom-api-returns-dynamodb-throttling-error-on-meeting-creation/132024/1 "2025-04-28T02:48:26Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
POST [https://api.zoom.us/v2/users/{userId}/meetings](https://api.zoom.us/v2/users/%7BuserId%7D/meetings)  
Creating a Zoom Meeting via the API

**Description**  
Description  
We encountered an error when trying to create Zoom meetings via the Zoom API from an AWS Lambda function. The error occurred while creating 8 Zoom meetings in a single request (the batch size for the day, as the number of meetings we create daily varies). Specifically, the error happened on one of the 8 meeting creation requests, while the other 7 requests were processed successfully.

Key Details:

We create a varying number of meetings daily, and in this case, we are creating 8 meetings.

The error occurred on one of the 8 requests, while the other 7 requests were processed successfully without issue.

We are using OAuth2 for authentication and calling the /meetings endpoint.

We do not use DynamoDB in our Lambda function.

The error seems related to Zoom’s internal system, possibly involving DynamoDB, as suggested by the error message.

**Error?**  
“{"code":-1,"message":"Throughput exceeds the current capacity of your table or index. DynamoDB is automatically scaling your table or index so please try again shortly. If exceptions persist, check if you have a hot key: [Best practices for designing and using partition keys effectively in DynamoDB - Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html) (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ThrottlingException; Request ID: 9GHNMVMQL42GD7LT42V1EN3G73VV4KQNSO5AEMVJF66Q9ASUAAJG; Proxy: null)"}”

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Request URL / Headers **(without credentials or sensitive info like emails, uuid, etc.)** / Body_  
[https://api.zoom.us/v2/users/{userId}/meetings](https://api.zoom.us/v2/users/%7BuserId%7D/meetings)

Headers  
{  
“Authorization”: “Bearer {access\_token}”,  
“Content-Type”: “application/json”  
}

Body  
{  
“topic”: “Vanessa\_Fr19b”,  
“type”: 2,  
“default\_password”: true,  
“settings”: {  
“registration\_type”: 2,  
“approval\_type”: 0  
},  
“start\_time”: “2025-04-25T19:20:00”  
}

_2. Authentication method or app type_  
OAuth2 (via Zoom OAuth token)

_3. Any errors_  
The error message described above is returned immediately after the request is made.

---

<div class="post-metadata">

**Author:** ![alexm](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alexm/32/67701_2.png) [@alexm](https://devforum.zoom.us/u/alexm)\
**Post date:** [April 28, 2025, 3:24pm UTC](https://devforum.zoom.us/t/zoom-api-returns-dynamodb-throttling-error-on-meeting-creation/132024/2 "2025-04-28T15:24:56Z")

</div>

The create meeting endpoint is rate limited as “medium” (2 per second) which may have something to do with it. Consider trying adding a artificial delay between requests.

---

<div class="post-metadata">

**Author:** ![ark](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@ark](https://devforum.zoom.us/u/ark)\
**Post date:** [April 29, 2025, 12:55am UTC](https://devforum.zoom.us/t/zoom-api-returns-dynamodb-throttling-error-on-meeting-creation/132024/3 "2025-04-29T00:55:26Z")

</div>

Thanks for the clarification.  
We’ll consider adding a delay between requests to avoid rate limit issues.
