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.

API reference Open your group settings

GET /v1/groups/{groupId}/roster
Authorization: Bearer wowutils_live_••••…

200 OK

X-RateLimit-Remaining: 59

{
  "memberCount": 24,
  "members": [
    {
      "displayName": "Thrall",
      "rank": "Raider",
      "characters": [{
        "name": "Thrall", "realm": "tarren-mill",
        "class": "Shaman", "spec": "Enhancement"
      }]
    },
    // …23 more members
  ]
}

The API is young and still growing. Build against the /v1 prefix, and keep an eye on the developer channel: we announce breaking changes there before they land.

What v1 gives you

Your group

The entry point: your group’s identity and links to everything below.

GET/v1/groupsthe groups your key can read
GET/v1/groups/{id}group identity and links

Roster

Members and their characters: name, realm, class and spec, rank, and who has claimed what. Your bot can manage members, too.

GET/v1/groups/{id}/rosterthe full roster
POST/v1/groups/{id}/roster/membersadd a member
PUT/v1/groups/{id}/roster/members/{memberId}edit a member
DELETE/v1/groups/{id}/roster/members/{memberId}remove a member

Raid resets & setups

Each week’s setups: boss order and the players in them. Read who’s in or benched per boss, or write the split from your own tool.

GET/v1/groups/{id}/resetslist resets
GET/v1/groups/{id}/resets/{resetId}one reset
GET/v1/groups/{id}/latest-resetthe current week
GET/v1/groups/{id}/latest-reset/setups/{setupId}/fulla full setup
PUT…/setups/{setupId}/bosses/{bossSlug}/assignmentsset the in/out split
PUT…/setups/{setupId}/players/{playerId}/activebench or activate
POST/v1/groups/{id}/latest-reset/setupscreate a setup
DELETE…/latest-reset/setups/{setupId}delete a setup

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.

GET/v1/groups/{id}/calendar-eventsevents and signups
GET/v1/groups/{id}/calendar-events/{eventId}one event
GET/v1/groups/{id}/calendar-schedulesrecurring schedules
GET/v1/groups/{id}/calendar-schedules/{scheduleId}one schedule
PUT…/calendar-events/{eventId}/signup/{memberId}set a signup
PUT…/signup/by-discord-user/{discordUserId}set a signup from Discord
GET…/calendar-events/{eventId}/readinesswho’s ready tonight

Notes & assignments

Structure and labels only: name, boss, difficulty, counts, timestamps. The contents are never returned.

GET/v1/groups/{id}/notesnote structure
GET/v1/notes/{noteId}one note
GET/v1/assignments/{assignmentId}one assignment block

Loot & droptimizers

Each player’s wishlist with its priorities and notes, and when each droptimizer was uploaded with a link to the full sim. Your bot can push a new droptimizer from a Raidbots or QE Live link, too.

GET/v1/groups/{id}/wishlistswishlists and priorities
GET/v1/groups/{id}/droptimizersdroptimizer freshness and links
POST/v1/groups/{id}/droptimizersimport a droptimizer

Changes feed

One feed that tells you when anything above changed, so you poll a single cheap endpoint instead of re-fetching everything.

GET/v1/groups/{id}/changeswhat changed since your last look

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 point budget

Each group gets an hourly budget of 60 points, raised to 225 then 600 as the group is boosted. Reading data costs 1 point, saving a change costs 2, and importing a droptimizer costs 5. The X-RateLimit-Remaining and X-RateLimit-Cost headers on every response tell you where you stand. We’re still tuning how much load the API can take, and may raise these limits over time.

Cached responses are free

Send the ETag back as If-None-Match. If nothing changed you get an empty 304 instead of the full payload, and a 304 costs nothing against your budget, so polling for changes is cheap.

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.

Reference & policies

Full API reference (Scalar)Terms of Service Acceptable Use Policy Data Handling note

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.