How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AniList OAuth2 API

OAuth2 authorization code and implicit grant endpoints

AniList OAuth2 API is one of 3 APIs that AniList publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://graphql.anilist.co, https://anilist.co.

3 operations 3 paths 2 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://graphql.anilist.co
Authentication
HTTP Bearer, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

AniList OAuth2 API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode and implicit flows. By default, every request must be authenticated, though some operations may also be called without credentials.

  • bearerAuth — OAuth2 access token issued by AniList. No scopes; access tokens grant (almost) full access to a user's data. Tokens are valid for one year.
  • oauth2 — AniList OAuth2 (no scopes supported)

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

OAuth2 3

OAuth2 authorization code and implicit grant endpoints

GET
/api/v2/oauth/authorize
Begin the OAuth2 authorization flow
oauthAuthorize 4 params → 302
POST
/api/v2/oauth/token
Exchange an authorization code for an access token
oauthExchangeToken body → 200400401
GET
/api/v2/oauth/pin
Display the OAuth2 auth pin for manual entry
oauthAuthPin → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TokenRequest (5 properties), TokenResponse (4 properties). Each schema is shown below with its type and property counts.

TokenRequest
object
5 properties 5 required
TokenResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anilist-oauth2-api-openapi.yml Raw ↑

Other APIs AniList publishes across the network.

AniList GraphQL API v2
AniList GraphQL API
Where this information came from

This is an independent, third-party profile of AniList OAuth2 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.