Introduction
V1 and V2 APIs are deprecated and are considered legacy APIs.
The Wynncraft API lets applications read public game, player, guild, item, leaderboard, map, and news data.
Base URL: https://api.wynncraft.com/v3
If you are migrating from a legacy API, most structures were kept familiar where practical. Some responses were reworked where the old shape was difficult to use, especially player stats.
API changelogs and upcoming changes are announced on the developer Discord and listed in changelog.
Caching
GET requests are cached with route-specific TTLs. Cached responses include standard cache headers such as Cache-Control and Expires.
Responses can come from different cache sources:
Throttling and Rate Limits
Rate limits are tracked per bucket. Current buckets are:
Each bucket is tracked independently. For example, using both PLAYER and GUILD buckets allows requests against each bucket separately.
See Authentication for authenticated request support.
Headers
The API includes quality-of-life HTTP headers:
Errors
Errors use a common format:
See Exceptions for the known exception list.
Multi-Selectors
Some queries can match multiple resources. In those cases, the API can return a MultipleObjectsReturned response with code 300 and an objects dictionary.
API Markup Parser
Some API fields contain rendered Wynncraft markup as HTML. The parser always emits predictable <span> elements.
Allowed style values:
text-decoration: underlinetext-decoration: line-throughfont-style: italicfont-weight: boldercolor: #XXXXXXmargin-left: 7.5pxmargin-left: 20px
Allowed classes:
Fonts are available on the CDN under https://cdn.wynncraft.com/nextgen/fonts.
Media URLs
Some responses include partial media paths. Complete those paths with the CDN base URL: https://cdn.wynncraft.com/nextgen
The API will never return the full URLs for assets coming from the CDN.
