Viserio Cooldowns API
For Developers
The API for your group roster, raid resets and setups, calendar, loot wishlists, and note structure. Build your own bots, sites, and sheets on your group’s data.
Still stabilizing. Build against the /v1 prefix and expect occasional refinements before it is marked stable. We will call out breaking changes in the developer channel.
What v1 gives you
Roster
Members and their characters: name, realm, class and spec, rank, and who has claimed what.
Raid resets & setups
Each week’s setups: boss order and the players in them. Pull the latest reset, or a full setup with who’s in or benched and the in/out split for each boss.
Calendar
Your scheduled raid nights and each event’s signups: who’s coming and in what role. Your own bot can set a raider’s attendance, too. Personal signup comments stay private.
Notes & assignments
Structure and labels only: name, boss, difficulty, counts, timestamps. The contents are never returned.
Loot & droptimizers
Each player’s wishlist with its priorities and notes, and when each droptimizer was uploaded with a link to the full sim, so you can see whose loot data is current. Your bot can push a new droptimizer from a Raidbots or QE Live link, too.
How access works
Per group, not per person
A group admin turns on API sharing in the group settings. It stays off until they do.
One key, sent in a header
Each group has a single key, shown once. Send it in the request Authorization header, never in a URL.
Hourly request quota
Each group gets 20 requests an hour, raised to 75 then 200 as the group is boosted. We’re still tuning how much load the API can take, and may raise these limits over time.
Conditional requests save bandwidth
Send the ETag back as If-None-Match. If nothing changed you get an empty 304 instead of the full payload. Every request still counts against the quota, so poll on a sensible interval.
Get started
- 1
Be a group admin
Only an admin can turn on sharing and manage the key. Not an admin? Ask your raid lead.
- 2
Open API Access
In your group, go to Settings, then API Access.
- 3
Create your key
Turn on sharing, tell us what you are building and how to reach you, and copy the key right away. It is shown once and cannot be recovered.
- 4
Make your first call
Send the key in the Authorization header. Start at the root and follow the links it returns to reach your group data.
Privacy by design
Only what a real flow needs
The API returns the data a coordination tool actually uses, not everything we hold. Note and assignment text never leaves; who claimed a spot is reduced to a yes/no.
Your data stays yours
A group admin opts in, and access stops the moment they opt out. We never collect email addresses, and the data is not ours to resell or build a public directory from.
Good faith with the game providers
We expose only Blizzard account data the member shared by signing in (their battletag and characters) and your own planning data. Anything you store has to honor Blizzard, Warcraft Logs, and Raider.io API terms too.
Feature requests
v1 covers the essentials. If you need something it does not do yet, tell us in Discord and ask for Penkek. Say what you are building and what you need next.
The API is offered as-is, with no uptime promise. It is rate limited and can be throttled to keep the site fast for everyone.