AniList · OAuth Scopes
AniList OAuth Scopes
OAuth 2.0
derived
AniList uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from https://anilist.co/api/v2/oauth/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
AnimeMangaEntertainmentMediaSocialDatabaseGraphQLOAuth2Public APIs
Scopes: 0
Flows: authorizationCode, implicit
Method: derived
OAuth endpoints
Authorization URL
https://anilist.co/api/v2/oauth/authorize
https://anilist.co/api/v2/oauth/authorize
Token URL
https://anilist.co/api/v2/oauth/token
https://anilist.co/api/v2/oauth/token
Flows
authorizationCodeimplicit
authorizationCodeimplicit
Scopes (0)
AniList implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
AniList's OAuth2 does not use scopes — the auth docs state "Scopes are not supported. Access tokens provide (almost) full access to a user's data" (https://docs.anilist.co/guide/auth/).
AniList's OAuth2 does not use scopes — the auth docs state "Scopes are not supported. Access tokens provide (almost) full access to a user's data" (https://docs.anilist.co/guide/auth/).
📄 Provider scope reference: https://docs.anilist.co/guide/auth/