canonical: https://jentic.com/apis/pathofexile.com/path-of-exile

# Path of Exile API

The Path of Exile API reads public game data and authenticated account data for the online action RPG, so an application can look up leagues, ladders, characters, and public stash tabs. You can list the current and past leagues and read a league's ladder, retrieve PvP matches and their details, and read the public stash tab stream that players use for trading. With an authenticated account you can read the account's profile, its characters, and its stash tabs for a given league.

## For AI agents

Read Path of Exile leagues, ladders, PvP matches, and public stash tabs, and read an authenticated account's profile, characters, and stash tabs. Authenticates with OAuth2 using the authorization code flow.

## Scope

Does not handle in-game purchases, account management, or writing to a character. Use for reading Path of Exile league, ladder, character, and public stash data only.

## Capabilities

- Read the list of active and past leagues
- Retrieve a league's ladder rankings
- Look up PvP matches and their details
- Read the public stash tab stream used for trading
- Read an authenticated account's profile and characters
- Read an account's stash tabs for a league

## Use cases

### Agent-Driven Ladder and League Lookups

An AI agent connected through Jentic reads the active leagues and a league's ladder so a player can ask about standings in plain language and get an answer. The agent lists the leagues first to resolve the one the player means, then reads its ladder.

Example prompt: Find the current challenge league and return the top ten characters on its ladder

### Character and Account Insights

With an authenticated account, an application reads the account's profile and characters so a companion tool can show a player's builds and progress. The tool reads the character list and then a named character's details to summarise its skills and level.

Example prompt: List my characters and return the level and class of my highest-level one

### Public Stash Trading Data

A trading tool reads the public stash tab stream to track items players have listed, so it can surface prices and availability. It pages through the stream to keep a view of the current market for an item.

Example prompt: Read the latest public stash tabs and list any entries offering the item I am watching

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/league` | List leagues |
| GET | `/league/{id}/ladder` | Get league ladder |
| GET | `/pvp-match` | List PvP matches |
| GET | `/public-stash-tabs` | Get public stash tabs |
| GET | `/account/profile` | Get account profile |
| GET | `/character` | List characters |

## Key resources

- **Leagues** — The active and past leagues that scope characters, ladders, and stashes
- **Ladders** — The ranked standings of characters within a league
- **Characters** — An authenticated account's characters, readable individually or as a list
- **Public stash tabs** — The stream of player-listed stash tabs used for trading

## Why Jentic

- **Setup:** Wiring the Path of Exile API by hand means running the OAuth2 authorization code flow, refreshing the token, and learning how leagues scope ladders, characters, and stashes. Through Jentic you install once, import Path of Exile from the API Directory, authorize once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow the public reads like leagues and ladders while leaving account and stash operations out. Because the league id sits in the URL path, a rule can pin the agent to one league's data, and every call it makes is logged.
- **Credential handling:** Your Path of Exile OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a league ladder' or 'list my characters', and Jentic returns the matching Path of Exile operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Steam Web API** — Reads player, game, and community data from the Steam platform
- **IGDB API** — Game metadata database covering titles, genres, and release information

## FAQ

### Is there a Path of Exile MCP server?

You don't need an MCP server to give your agent the Path of Exile API. Jentic connects it directly from the API Directory: import it, authorize once, and your agent can read leagues, ladders, and characters straight away, with no extra server to run and no tool definitions to load into the agent's context.

### Can I limit what my agent is allowed to do with the Path of Exile API?

Yes. You choose which operations your agent may call, so you can allow reading leagues and ladders while leaving account profile and stash operations out. Because the league id sits in the URL path, a rule can also limit the agent to one league's data, and every call it makes is logged.

### What authentication does the Path of Exile API use?

The Path of Exile API authenticates with OAuth2 using the authorization code flow per its OpenAPI spec, and requests carry the resulting access token. Through Jentic the token is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

### Can I read a player's characters with the Path of Exile API?

Yes. With an authenticated account the API reads the account's profile and its characters, and it can return a named character's details. It also reads the account's stash tabs for a league, so an agent can summarise a player's builds and holdings.

### What are the rate limits for the Path of Exile API?

The OpenAPI spec does not specify rate limits for the Path of Exile API. For current limits and developer terms, see the Path of Exile developer documentation at https://www.pathofexile.com/developer/docs.

### How do I read Path of Exile data through Jentic?

Import the Path of Exile API from the Jentic API Directory, then have your agent issue a request such as 'get the ladder for the current league'. Jentic matches the intent to the right read operation and returns its input schema so the agent builds the correct request, with your authorization handled at call time.