Wynncraft APIwynncraft.com ↗
Access Wynncraft game data via 8 endpoints: item database, player stats, character lists, guild rosters, and global search across players, guilds, and items.
What is the Wynncraft API?
The Wynncraft API provides 8 endpoints covering the full breadth of Wynncraft MMORPG game data, from a paginated item database with tier and type filtering to individual player statistics and guild rosters. The get_player_stats endpoint returns fields like playtime, guild membership, mobsKilled, chestsFound, totalLevel, and completed quests. The global_search endpoint lets you query across players, guilds, and items in a single request.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/5adcf1d6-306a-494c-a4ba-0443cbd08b74/get_item_metadata' \ -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 wynncraft-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.
"""
Wynncraft API - Usage Example
Get your API key from: https://parse.bot/settings
"""
from parse_apis.Wynncraft_API import Wynncraft, ItemTier, CharacterClass, PlayerNotFound
wynncraft = Wynncraft(api_key="YOUR_API_KEY")
# Search for mythic-tier weapons
for item in wynncraft.items.search(filters='{"type":["weapon"],"tier":["mythic"]}', limit=5):
print(item.display_name, item.tier, item.sub_type)
# Browse the full item database (paginated automatically)
for item in wynncraft.items.list(limit=3):
print(item.display_name, item.type, item.tier)
# Get player stats and list their characters
player = wynncraft.players.get(username="Salted")
print(player.username, player.playtime, player.online)
for char in player.characters.list(limit=3):
print(char.uuid, char.type, char.level, char.total_level)
# Look up a guild by name
guild = wynncraft.guilds.get(name="Avicia")
print(guild.name, guild.prefix, guild.level, guild.wars)
# Global search across players, guilds, and items
results = wynncraft.discoveries.find(query="warrior")
print(results.query)
for item in results.items[:3]:
print(item.display_name, item.tier)
# Typed error handling for a non-existent player
try:
wynncraft.players.get(username="zzzNoPlayer999")
except PlayerNotFound as exc:
print(f"Player not found: {exc.username}")
print("exercised: items.search / items.list / players.get / characters.list / guilds.get / discoveries.find")
Returns metadata for item filters and identifications. Includes possible values for types, tiers, attack speeds, identification stat names, major IDs, and level ranges.
No input parameters required.
{
"type": "object",
"fields": {
"static": "object mapping identification/type names to numeric IDs",
"filters": "object containing type arrays, tier lists, identification names"
},
"sample": {
"data": {
"static": {
"bow": 488,
"weapon": 489
},
"filters": {
"tier": {
"items": [
"common",
"unique",
"rare",
"legendary",
"fabled",
"mythic",
"set"
]
},
"type": [
"weapon",
"armour",
"accessory"
]
}
},
"status": "success"
}
}About the Wynncraft API
Item Data
The item endpoints cover metadata, browsing, and search. get_item_metadata returns filter reference data: identification stat names, type arrays, tier lists, attack speeds, and major IDs — useful for building filter UIs or validating inputs before querying. get_item_database_paginated returns 20 items per page, with a controller object carrying count, pages, prev, current, and next for navigation. Each item object includes displayName, type, subType, tier, identifications, base stats, and requirements. get_item_database_full iterates all pages and returns the complete database in one call, though it may take up to 60 seconds. search_items accepts a JSON filter object with keys like type (weapon, armour, accessory) and tier (common, unique, rare, legendary, fabled, mythic, set), returning paginated results with the same controller structure.
Player and Character Data
get_player_stats takes a case-insensitive username and returns online, server, playtime, rank, and a guild object with name, prefix, and rank. The globalData field contains aggregate stats: wars, totalLevel, mobsKilled, chestsFound, dungeons, raids, pvp, and completedQuests. get_player_characters returns an array of character objects per player, each with uuid, type (WARRIOR, ARCHER, MAGE, ASSASSIN, SHAMAN), level, xp, xpPercent, totalLevel, gamemode, and optional reskin and nickname fields.
Guild and Search Data
get_guild_stats takes a case-insensitive guild_name and returns level, wars, territories, prefix, season ranks, banner data, and a members object organized by rank tiers: owner, chief, strategist, captain, recruiter, and recruit. Each member entry includes UUID, online status, contributed XP, join date, and globalData. global_search accepts a query string and returns results split into players (UUID-to-object map with username and rank), guilds and guildsPrefix (UUID-to-object maps with name, prefix, level, members, and created date), and items (array of matching item objects).
The Wynncraft API is a managed, monitored endpoint for wynncraft.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wynncraft.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 wynncraft.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?+
- Compare item identifications and tier across weapon or armour sets using search_items filters
- Display a player's aggregate stats dashboard using playtime, mobsKilled, chestsFound, and completedQuests from get_player_stats
- List all characters on an account with their class type, level, and gamemode via get_player_characters
- Render a guild member roster organized by rank using the members object from get_guild_stats
- Build an autocomplete search tool for players, guilds, and items using global_search
- Populate item filter dropdowns by fetching identification names and tier lists from get_item_metadata
- Track guild territory holdings and war counts over time using the territories and wars fields from get_guild_stats
| 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 Wynncraft have an official developer API?+
What does the search_items endpoint filter on, and what happens when no items match?+
type (weapon, armour, accessory), tier (common, unique, rare, legendary, fabled, mythic, set), and other item properties. Results are paginated at 20 per page with a controller object for navigation. When no items match the criteria, the results array is empty and the controller reflects zero count and pages.How is guild member data structured in get_guild_stats?+
members object contains a total count and sub-objects keyed by rank: owner, chief, strategist, captain, recruiter, and recruit. Each member entry holds UUID, online status, contributed XP, join date, and a globalData block with aggregate stats for that member.Does the API return individual character inventory or skill tree data?+
How does get_item_database_full handle the complete dataset, and is there a timeout risk?+
items object plus a total count. The endpoint documentation notes this can take up to approximately 60 seconds. For latency-sensitive applications, using get_item_database_paginated with explicit page numbers gives more control over request timing.