GraphQL rate limits

Beta

Zoom GraphQL is in a public beta.

GraphQL rate limits follow the same rate limit rules as the Zoom RESTful APIs. See Rate limits for details.

Queries and mutations are limited at the field (or object) level. When you request additional fields, those cost toward the daily rate limit count. For example, one field, such as listing users, would be limited similarly to REST API List user request. Two fields, such as get user ID and list user's meeting, would be limited similarly to both a REST API request to get the user ID and another to list the user's meeting.

GraphQL query user field = one list user API request

{
    users {
        edges {
            id
        }
    }
}

GraphQL query user profile and meetings fields = one get user API request + one list user's meeting API request

The following example queries a user's first name in their profile and lists their first 10 scheduled meetings. The profile and meetings objects each have their own rate limit.

{
    user(userId: "me") {
        profile {
            firstName
        }
        meetings(meetingType: SCHEDULED, first: 10) {
            edges {
                id
            }
        }
    }
}

Additionally, when sending multiple objects in one request, the rate limit on the parent field determines whether operations on child fields resolve or not. For example, if you reach the rate limit for the parent field, user, in the previous example, the query will not run for the child fields, profile or meetings below it.

Rate limit tables

See the following tables for rate limits for queries and mutations.

• Rate limit tables
• Queries
• Mutations

Queries

Mutations