Wowhead APIwowhead.com ↗
Access Wowhead data via API: search items, NPCs, spells, and quests by ID, browse paginated database lists, and fetch WoW news and live game events.
What is the Wowhead API?
This API exposes 9 endpoints covering the Wowhead World of Warcraft database, including item detail lookup via get_item, paginated database browsing via get_database_list, and live game event schedules via get_today_in_wow. Item responses include 10 structured fields such as quality tier, item level, subclass, icon identifier, and raw equip stats JSON. NPC, spell, and quest endpoints return name and canonical URL by numeric ID.
curl -X GET 'https://api.parse.bot/scraper/93b56483-7fc6-48da-bd9f-1310e3bca1c3/search?query=Thunderfury' \ -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 wowhead-com-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.
"""Walkthrough: Wowhead SDK — search items, look up details, browse news."""
from parse_apis.wowhead_api import Wowhead, DatabaseCategory, NewsCategory, Region, EntityNotFound
client = Wowhead()
# Search across all categories for a legendary weapon
result = client.searchresults.query(query="Thunderfury")
print(f"Search returned data with {len(result.data)} entries")
# Get detailed item info by ID
item = client.items.get(id="19019")
print(f"Item: {item.name}, Quality: {item.quality}, Level: {item.level}")
# Look up an NPC by ID
npc = client.npcs.get(id="15956")
print(f"NPC: {npc.name}, URL: {npc.url}")
# Browse popular NPCs from the database list
db_result = client.databaseresults.list(category=DatabaseCategory.NPCS)
print(f"Database list: {db_result.count} NPCs in category {db_result.category}")
for entry in db_result.results[:3]:
print(f" - {entry.name} (popularity: {entry.popularity})")
# Get latest news and drill into an article
feed = client.newsfeeds.get(category=NewsCategory.ALL)
print(f"News feed: {feed.count} articles")
if feed.items:
summary = feed.items[0]
print(f" Latest: {summary.title} ({summary.pub_date})")
article = summary.details()
print(f" Author: {article.author}, Content length: {len(article.content_raw or '')}")
# Typed error handling for a non-existent item
try:
client.items.get(id="9999999")
except EntityNotFound as exc:
print(f"Entity not found (expected): {exc}")
# Get today's WoW events for US region
today = client.todayinwows.get(region=Region.US)
print(f"Today in WoW ({today.region}): {len(today.data)} event groups")
for group in today.data[:2]:
print(f" - {group.name} (id: {group.id})")
print("Exercised: searchresults.query / items.get / npcs.get / databaseresults.list / newsfeeds.get / article.details / todayinwows.get")
Full-text search across all Wowhead database categories (Items, NPCs, Spells, Quests, etc.). Returns the query string and an object with results grouped by category. Each category key contains an array of matching entities with their metadata.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. 'Thunderfury', 'Fireball'). |
{
"type": "object",
"fields": {
"data": "array containing the search query string at index 0 and an object at index 1 with category-grouped results (e.g. items, npcs, spells, quests keys each holding arrays of matching entities)"
},
"sample": {
"data": [
"Thunderfury",
{
"items": [
{
"id": 19019,
"icon": "inv_sword_39",
"name": "Thunderfury, Blessed Blade of the Windseeker",
"level": 29,
"quality": 5
}
]
}
],
"status": "success"
}
}About the Wowhead API
Item, NPC, Spell, and Quest Lookups
The get_item endpoint accepts a Wowhead item ID and returns 10 fields: id, name, icon, link, class, subclass, level, quality, json, and jsonEquip. The quality field maps to tier names like Legendary or Epic; jsonEquip contains raw stat data suitable for parsing into numeric attributes. By contrast, get_npc, get_spell, and get_quest each return only id, name, and url — useful for resolving a numeric ID to a display name and canonical page link.
Database List and Search
The get_database_list endpoint accepts a category parameter (items, npcs, spells, or quests) and an optional page integer, returning up to 50 results sorted by popularity. The response includes a count field and a results array whose shape varies by category — NPC entries include level, while item entries include a raw data blob. The search endpoint accepts a free-text query and returns results grouped into category buckets (items, npcs, etc.), making it suitable for autocomplete or cross-entity lookup.
News and Events
get_news fetches up to 40 articles per request from the Wowhead RSS feed. The optional category parameter accepts values like retail, classic, classic-era, classic-seasonal, diablo, and diablo-4, defaulting to all. Each article in the items array includes title, link, pubDate, category, and description. For full article body, get_news_article accepts a full article URL or news ID and returns title, author, and content_raw in BBCode markup.
Today in WoW Events
get_today_in_wow accepts a region parameter (US or EU) and returns an array of event group objects. Each object includes id, name, regionId, and a groups array with detailed event information. The response also includes a timestamp field in ISO 8601 UTC indicating when the data was fetched, useful for cache invalidation in applications tracking daily reset content.
The Wowhead API is a managed, monitored endpoint for wowhead.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wowhead.com 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 wowhead.com 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 WoW item comparison tool using
get_itemquality, level, class, subclass, and equip stats fields. - Populate an autocomplete search bar for WoW entities using the
searchendpoint's category-grouped results. - Track current WoW daily events and raid availability by polling
get_today_in_wowfor US and EU regions. - Aggregate WoW news feeds by game version (retail, classic, classic-era) using
get_newswith the category filter. - Resolve NPC or spell IDs from combat log data to display names using
get_npcandget_spell. - Build a WoW news reader that fetches article summaries via
get_newsand full BBCode content viaget_news_article. - Paginate through the most popular items or NPCs in a category using
get_database_listfor bulk data collection.
| 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 Wowhead have an official public developer API?+
What does `get_item` return beyond a name and icon?+
name and icon, get_item returns class (e.g. Weapons), subclass (e.g. One-Handed Swords), level (item level), quality (tier name such as Legendary or Epic), json (raw item data JSON), jsonEquip (raw equip stat JSON), and a link pointing to the canonical Wowhead item page.Does the API return tooltip HTML or stat breakdowns for spells, quests, and NPCs the way it does for items?+
get_item. The get_npc, get_spell, and get_quest endpoints each return only id, name, and url. You can fork the API on Parse and revise it to add richer detail endpoints for those entity types.How fresh is the data returned by `get_today_in_wow`?+
get_today_in_wow response includes a timestamp field in ISO 8601 UTC indicating when the event data was fetched. You can compare this against the current time to determine data age. WoW daily resets vary by region — US and EU have different reset times — which is why the endpoint accepts a region parameter.Can I retrieve item or NPC data for WoW Classic separately from retail?+
get_news endpoint supports Classic-specific categories (classic, classic-era, classic-seasonal), but the item, NPC, spell, and quest lookup endpoints do not currently accept a game-version parameter — they target the main Wowhead database. You can fork the API on Parse and revise it to point lookups at the Wowhead Classic subdomain for Classic-specific entity data.