Hello Zoom Developer Support team,
I am writing to request a review and, if appropriate, an INCREASE of API rate limits for our production integration with Zoom. This is a legitimate LMS use case; we are not scraping or abusing the API.
────────────────────────────────
- Organization and product
────────────────────────────────
• Company / product name: [e.g. Esampark Tech Solutions/ Medh]
• Description: [e.g. We operate an LMS for online classes with batches, multiple instructors, and students who receive join links for scheduled sessions.]
• Environment: PRODUCTION
────────────────────────────────
2) Zoom application (for your reference)
────────────────────────────────
• Integration: Server-to-Server OAuth (or specify if different)
• App name: Medh
• Client ID (public identifier only): LuU4xCjBRkG_Ki_Sq8rBCQ
• API usage in plain language: [e.g. We create and/or update one Zoom meeting per scheduled class session so students receive the correct join URL from our LMS.]
────────────────────────────────
3) Business / LMS use case
────────────────────────────────
• Scheduling: [e.g. Admins or instructors finalize schedules in our app; the system then provisions Zoom meetings for each session.]
• Triggers: [e.g. Primarily when publishing a schedule, bulk “generate meeting links” for a batch, or when session times are updated.]
• Not: [e.g. We are not making Zoom calls on every page view from students.]
────────────────────────────────
4) Volume (approximate is OK)
────────────────────────────────
• Approx. active or enrolled students (relevant period):1000
• Instructors or hosts using Zoom via this integration:30
• Typical API-heavy days:every day
• Peak region / timezone:ist
• Rough estimate – meeting create/update per DAY on a busy day: 1000
• BIGGEST BURST: [e.g. In one admin action, up to __ meetings created or updated within __ minutes] — this is our main reason for contact.
We expect this to [remain similar / grow to …] in the next [3–6] months.
────────────────────────────────
5) Zoom account (organization)
────────────────────────────────
• Account type: Pro
• Licensed host users (if known): All the 23 Users who are there in the account (neeraj@esampark.biz) this is the admin Account Email
────────────────────────────────
6) What problem we see
────────────────────────────────
• We hit rate limiting (e.g. HTTP 429 or documented rate limit errors) when: [short description, e.g. bulk link generation, back-to-back scheduling, etc.]
• Approx. date/time (UTC if possible): [when it last happened]
• Error summary (no secrets, no access tokens, no full response bodies with PII):
- Status: [e.g. 429]
- Message: [short excerpt from your logs]
• We already: [e.g. use queuing, spacing, or retries] — if applicable.
────────────────────────────────
7) What we are asking for
────────────────────────────────
Please evaluate our use case and approve a SUITABLE HIGHER LIMIT for this production application (e.g. daily and/or per-minute/second as applicable to the endpoints we use), so our LMS can run reliably at the volumes above.
We can provide more metrics, redacted logs, or a short call if helpful.
Thank you.
Name: Harsh Patel
Work email: it@esampark.biz
Role: Cloud & DevOps Administrator
Company: Esampark Tech Solutions Pvt. Ltd.