poedb APIpoedb.tw ↗
Access Path of Exile item stats, skill gems, passives, league info, and category listings for both PoE 1 and PoE 2 via the poedb.tw API.
What is the poedb API?
The poedb.tw API exposes 4 endpoints covering Path of Exile game data across both PoE 1 and PoE 2, including item stats, skill gem details, passive nodes, and league history. The get_details endpoint returns structured sections with tables and text for any entity slug — items like Headhunter, skills like Fireball, or mechanics like Bleeding. The search endpoint lets you resolve entity names to slugs before fetching full records.
curl -X GET 'https://api.parse.bot/scraper/9216ce94-1acd-456a-b0bb-9b2fa05ab44c/search?query=Fireball&version=poe1' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace poedb-tw-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.poedb_api import PoEDB, GameVersion, Entity, EntityDetail, WikiCategory, League
# Initialize the client
poedb = PoEDB()
# Search for entities matching "Fireball"
for entity in poedb.entities.search(query="Fireball", version=GameVersion.POE1):
print(entity.label, entity.value, entity.desc, entity.entity_class)
# Fetch detailed information for a specific entity by slug
detail = poedb.entitydetails.get(slug="Headhunter", version=GameVersion.POE1)
print(detail.name, detail.url)
for section in detail.sections:
print(section.title, section.text[:80])
# Browse a wiki category page
gem_category = poedb.wikicategories.get(category="Gem", version=GameVersion.POE1)
print(gem_category.category)
for card in gem_category.cards:
print(card.title, len(card.items))
# Get league information
league_data = poedb.leagues.get(version=GameVersion.POE1)
print(league_data.category)
for card in league_data.cards:
print(card.title, len(card.items))
Search for game entities (items, gems, passives, monsters, etc.) by keyword against the autocomplete index. Returns matching labels and their URL slugs. Performs a case-insensitive substring match on entity labels. The full index is fetched on each call so broad queries may return many results.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword to match against entity labels (case-insensitive substring match) |
| version | string | Game version: 'poe1' or 'poe2' |
{
"type": "object",
"fields": {
"results": "array of objects with label, value, desc, and class fields"
},
"sample": {
"data": {
"results": [
{
"desc": "Wiki",
"class": "",
"label": "Fireball",
"value": "Fireball"
},
{
"desc": "Wiki",
"class": "",
"label": "Vaal Fireball",
"value": "Vaal_Fireball"
}
]
},
"status": "success"
}
}About the poedb API
Searching and Resolving Entities
The search endpoint accepts a query string and an optional version parameter (poe1 or poe2) and returns an array of matching entities. Each result includes a label (display name), value (URL slug usable in get_details), desc (short description), and class (entity type such as gem, item, or passive). This is the primary way to discover slugs before fetching full records.
Entity Detail Pages
The get_details endpoint takes a slug — obtained from search results or known in advance — and returns the full structured page for that entity. The response includes the entity's name, canonical url, and a sections array. Each section has a title, one or more tables (row/column data for stats, modifiers, and level scaling), and optional text content. This covers items, gems, keystones, ailments, and other game objects.
Category Browsing
The get_category_data endpoint accepts a category string matching URL path segments used by poedb.tw — examples include Unique_item, Gem, League, Maps, and Bleeding. It returns a cards array where each card has a title and an items list with tabular properties for every entry in that category. This is useful for bulk lookups across an entire item class or mechanic type.
League Data
The get_leagues endpoint returns league information for PoE 1 or PoE 2 depending on the version parameter. The response is structured as cards, each containing a list of leagues with associated metadata such as name, duration, and dates. The category field in the response is always set to 'League'.
The poedb API is a managed, monitored endpoint for poedb.tw — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when poedb.tw changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official poedb.tw API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a loot filter tool that resolves item names to full stat blocks using
searchthenget_details - Populate a league history timeline using
get_leaguesfor both PoE 1 and PoE 2 - Generate a reference sheet of all unique items by fetching the
Unique_itemcategory viaget_category_data - Look up skill gem level-scaling tables for a build planner using
get_detailswith a gem slug - Track all map tiers and properties for a mapping tool via the
Mapscategory endpoint - Resolve passive node descriptions and modifiers for a passive tree analyzer using
get_details - Compare ailment mechanics like Bleeding or Poison by fetching their category and detail pages
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does poedb.tw have an official developer API?+
What does the `get_details` endpoint return for a skill gem like Fireball?+
sections array where each section contains a title, tables with row-and-column data (e.g., level scaling, damage values, mana costs), and optional text content. The top-level response also includes the entity's display name and canonical url on poedb.tw.Can I filter `get_category_data` results by item base type or modifier?+
items arrays. You can fork this API on Parse and revise it to add a filter parameter that narrows results before returning them.Does the API expose Path of Exile trade prices or real-time economy data?+
Is pagination supported for large category responses?+
get_category_data endpoint returns all available cards for a category in a single response without pagination parameters. For very large categories, the full payload is returned at once. If you need paginated access, you can fork this API on Parse and revise it to add offset or page parameters.