Viserio Cooldowns API

Back to For Developers

Viserio Cooldowns API: Terms of Service

The rules for using the API: how keys work, what stability to expect, and where liability sits.

Effective: 2026-06-07. API version: v1. Still stabilizing.

1. Acceptance

By creating an API key or making any request to api.wowutils.com you agree to these Terms, the Acceptable Use policy, and the Data Handling note. If you do not agree, do not use the API.

2. Eligibility and keys

  • An API key belongs to a group, not to a person. A group admin creates and manages the group’s single key from the group settings.
  • A group can use the API once a group admin has enabled API sharing. A supporter boost is not required for access; it raises the group’s request quota. Access stops automatically if API sharing is disabled.
  • Each group has at most one key. Regenerating it revokes the old one and does not reset usage quotas, which are tracked per group.
  • The key is a shared group credential. Any admin of the group is responsible for keeping it secret and for activity under it. Send the key only in the Authorization request header, never in URLs.
  • When the key is created you tell us what kind of integration it is and give an honest description of what it does, kept current if that changes. You may also leave a contact handle so we can reach you about your integration. This is how we understand how the API is used in this early version; feature requests go through Discord, not these fields.

3. Stability and availability

v1 is still stabilizing. Endpoints, response shapes, limits, and availability may change, break, or be withdrawn at any time, and there is no uptime, support, or backward-compatibility commitment. Build defensively and pin to /v1. Material changes are announced in the developer channel; we may still change things without notice to protect the service.

4. Good-faith use

You must use the API in good faith.

  • Do not use the API in a way that exposes other people’s information, such as the Battle.net battletags of guild members, where those members have not agreed to that exposure. The group admin opt-in is a gate, not a substitute for your own judgement about your members.
  • Intentional probing, enumeration, or any attempt to reach data you are not entitled to is prohibited. We run automated abuse detection and will act on it, including throttling, suspending, or revoking keys and blocking IP addresses, without notice.
  • Full rules are in the Acceptable Use policy.

5. Third-party and commercial use

  • You may integrate the API into third-party tools, including commercial services and apps.
  • Any tool that consumes this API must respect the API terms of the upstream providers (Blizzard’s Battle.net / World of Warcraft, Warcraft Logs, and Raider.io) for the storage and display of game and account data.
  • You may not create a permanent mirror of the data. Cached data must be deleted within 30 days unless it is refetched from the API. A refresh-based cache that re-fetches and expires data is acceptable; a permanent copy is not. See the Data Handling note for detail.

6. Data

The API exposes group-owned data, including battletags and character names, for groups that opted in. Your handling of that data is governed by the Data Handling note. You must stop using and delete a group’s data when that group’s access is removed or its opt-in is withdrawn.

7. Termination

We may suspend or terminate access at any time, including for policy violations or to protect infrastructure. A group admin may disable API sharing or revoke the group’s key at any time.

8. Disclaimer and liability

The API is provided “as is” and “as available”, without warranties of any kind. To the maximum extent permitted by law, Viserio Cooldowns and its maintainers are not liable for any damages arising from use of, or inability to use, the API.

9. Security disclosure

Report suspected vulnerabilities privately to [email protected] or to Penkek on Discord. Do not publicly disclose or exploit them.

10. Changes

We may update these Terms. Continued use after a change constitutes acceptance.

11. Contact

For questions, concerns, or issues, email [email protected] or message Penkek on Discord.