Skip to content

API reference

The raw API maps Riot endpoints to typed Python methods under riot.raw. Async and sync clients expose the same operation names and keyword-only parameters. Use this reference when you know the endpoint you need; use game workflows for tasks such as resolving a player and fetching their match history.

Browse by game

  • Accounts

    Resolve Riot IDs and PUUIDs, and discover a player's active shard or region.

    Common operations

  • League of Legends

    Matches, timelines, ranked entries, spectator data, mastery, and challenges.

    League operations

  • Teamfight Tactics

    Match history, ranked ladders, summoners, and spectator data.

    TFT operations

  • VALORANT

    Matches, ranked leaderboards, content, and service status.

    VALORANT operations

  • Legends of Runeterra

    Match data, ranked leaderboards, and service status.

    Runeterra operations

  • Riftbound

    Card-set content from the generated Riftbound API surface.

    Riftbound operations

For public League champion and item assets, see Data Dragon.

Read an operation entry

The raw operation inventory is generated with the SDK. Each row links a stable Riot operation ID to its Python accessor, HTTP method, route family, authentication mode, and response type.

Column How to use it
Operation ID Identify an operation in the registry, dispatcher, or MCP discovery.
Python accessor Call the endpoint on riot.raw with keyword-only arguments.
Method Check whether the endpoint reads or changes data.
Route Choose a supported platform, regional, or VALORANT route.
Auth Determine whether the operation requires an API key or an RSO token.
Result See the response type returned after validation.

Inspect inputs in Python

The registry includes input schemas and allowed routes for runtime discovery:

from riotskillissue.api.registry import OPERATION_REGISTRY

operation = OPERATION_REGISTRY["match-v5.getMatch"]
print(operation.accessor_path)
print(operation.input_schema)
print(operation.allowed_routes)

To make your first raw request, follow the runnable status example.

Coverage and authentication

Generated endpoints follow the community-maintained riotapi-schema feed, which scrapes Riot's API reference. The feed is not an official Riot specification. An operation's presence in the SDK does not grant access to it: availability depends on your Riot application, game permissions, and credentials.

Requirement Guide
Set an API key and client defaults Configuration
Choose a route or override the default Routing
Call an endpoint that requires a player's authorization Riot Sign On
Understand how the schema stays current Code generation

Changing the generated reference

Update tools/templates/api_reference.md.j2 and regenerate the SDK. Direct edits to docs/api-reference.md are replaced during generation.