Note
Consider building a GitHub App instead of an OAuth app. The rate limit for GitHub Apps using an installation access token scales with the number of repositories and number of organization users. Conversely, OAuth apps have lower rate limits and do not scale. For more information, see Differences between GitHub Apps and OAuth apps and About creating GitHub Apps.
About rate limits for OAuth apps
OAuth apps act on behalf of a user, by making requests with a user access token after the user authorizes the app. For more information, see Authorizing OAuth apps.
The generation of these user access tokens is subject to a rate limit. Additionally, API requests made with these user access tokens are subject to rate limits.
Rate limits for signing in users
OAuth apps should always cache their tokens, and only rarely need to sign in a user. Repeatedly signing in a user can indicate a bug, most frequently seen as an infinite loop between the app and GitHub. If an app signs the user in ten times within one hour, the next sign in within the same hour will require re-authorization of the application. This ensures the user is aware that the app is minting so many tokens, and provides a break in what may be an infinite loop otherwise. This ten sign in rate limit is distinct from the ten token limit also enforced for OAuth apps. For information about the ten token limit, see Authorizing OAuth apps.
Rate limits for the API
API rate limits are disabled by default for GitHub Enterprise Server. Contact your site administrator to confirm the rate limits for your instance.
If you are a site administrator, you can set rate limits for your instance. For more information, see Configuring rate limits.
If you are developing an app for users or organizations outside of your instance, the standard GitHub rate limits apply. For more information, see Rate limits for the REST API and Rate limits and node limits for the GraphQL API in the GitHub Free documentation.