canonical: https://jentic.com/apis/riotgames.com/riotgames

# Riot Games API

The Riot Games Developer API provides access to game data for League of Legends, Teamfight Tactics, Legends of Runeterra, and VALORANT. Retrieve summoner profiles, match history, ranked statistics, champion mastery, league standings, and more. The API exposes 24 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically get account by puuid, get account by riot id. Covers 24 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Get account by PUUID
- Manage social media data programmatically
- Integrate Riot Games API into automated workflows
- Query and filter Riot Games API records by parameters
- Monitor Riot Games API operational status and events

## Use cases

### Social Media Operations

Use the Riot Games API to perform social media operations programmatically. The API provides 24 endpoints covering core functionality including get account by puuid, get account by riot id, get current account.

Example prompt: Call GET /riot/account/v1/accounts/by-puuid/{puuid} to get account by puuid

### Automated Account Management

Automate account operations by combining multiple Riot Games API endpoints. Agents can get account by riot id and then get current account in a single workflow.

Example prompt: Call GET /riot/account/v1/accounts/by-riot-id/{gameName}/{tagLine} to get account by riot id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Riot Games API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'get account by puuid', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /riot/account/v1/accounts/by-puuid/{puuid} | Get account by PUUID |
| GET | /riot/account/v1/accounts/by-riot-id/{gameName}/{tagLine} | Get account by Riot ID |
| GET | /riot/account/v1/accounts/me | Get current account |
| GET | /lol/summoner/v4/summoners/by-puuid/{encryptedPUUID} | Get summoner by PUUID |
| GET | /lol/summoner/v4/summoners/{encryptedSummonerId} | Get summoner by ID |
| GET | /lol/champion-mastery/v4/champion-masteries/by-puuid/{encryptedPUUID} | Get all champion mastery entries |
| GET | /lol/champion-mastery/v4/champion-masteries/by-puuid/{encryptedPUUID}/by-champion/{championId} | Get champion mastery by champion ID |
| GET | /lol/champion-mastery/v4/champion-masteries/by-puuid/{encryptedPUUID}/top | Get top champion masteries |

## Key resources

- **Account** — Riot Account endpoints (regional routing)
- **Summoner** — Summoner profile data (platform routing)
- **Champion Mastery** — Champion mastery data (platform routing)
- **Champion** — Champion rotation data (platform routing)
- **League** — Ranked league data (platform routing)

## Why Jentic

- **Setup:** Wiring the Riot Games API by hand means passing your key in the X-Riot-Token header, optionally running the Riot Sign On OAuth flow for user endpoints, and routing every call to the correct regional host such as americas or europe. Through Jentic you install once, import the Riot Games API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Riot Games puts the identifier in the URL path (/riot/account/v1/accounts/by-puuid/{puuid}, /lol/summoner/v4/summoners/{encryptedSummonerId}), so a rule can pin your agent to one account or summoner and its lookups. You choose the operations it may call, and since these are read-only account and mastery reads the agent has no write path unless you add one.
- **Credential handling:** Your Riot Games API key and OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an account by riot id' or 'look up champion mastery', and Jentic returns the matching Riot Games API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Riot Games API use?

The Riot Games API uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get account by puuid with the Riot Games API?

Yes. Use the GET /riot/account/v1/accounts/by-puuid/{puuid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Riot Games API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get account by puuid through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account by puuid'. Jentic returns the matching Riot Games API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Riot Games API have?

The Riot Games API exposes 24 endpoints covering account, summoner, champion mastery operations.

### Can I limit what my agent is allowed to do with the Riot Games API?

Yes. Because you self-host Jentic One, your own rules decide which Riot Games API operations and credentials the agent may use. Since the identifier sits in the URL path (for example /riot/account/v1/accounts/by-puuid/{puuid} and /lol/summoner/v4/summoners/{encryptedSummonerId}), you can pin the agent to one account or summoner and its lookups, and pick exactly which operations it may call. These are read-only account, summoner, and champion-mastery reads, so the agent has no write path unless you grant one.