Web Tools for WoW Nerds
There are a couple of JSON feeds available for anyone that wants some of the raidbots data in an easy-to-parse format.
- If you can use gzip, please do.
- Be respectful, don’t spam the site. General rule of thumb is keep your activity to 1 request every 10 seconds.
- If you use this data on a public website, link back to raidbots.com and worldoflogs.com.
- Data is subject to change as I use some of these on raidbots itself. The most likely change is that additional fields will be added so that shouldn’t break most parsers but just be aware.
DPS Bot – Boss Aggregate Data
More information on Spec IDs at the bottom of this post.
Example of this feed:
Boss must match the case and format used in the URLs on raidbots. Names must be capitalized properly, spaces should be replaced with underscores, apostrophes should be rendered as the actual character and not the URL encoded % value.
Difficulty is one of the following:
Again, difficulty must be the capital letter. Lowercase will not work.
The data follows this format:
Measures are the following and map to various percentiles (minimum, maximum, median, and various percentiles of D/HPS):
Each measure contains an array of chart data. Each is a pair of a date and a value. The date is measure in milliseconds so you might need to divide by 1000 (or cut off the last 3 zeroes) to treat it a UNIX timestamp.
For anyone curious, EBCD stands for Epeen Bot Chart Data. This JSON feed is used by Epeen Bot to render the percentile charts.
Epeen Bot – Player Data
The basic rule of the URL format for this feed is that it’s the same as Epeen Bot. Find yourself (or a player you want to find out how to format the URL for) and take the path after /epeenbot/ and plug it into the feed URL.
Region is any of the valid Blizzard regions. US, EU, TW, etc. Lowercase.
Realm ideally should lowercase. Spaces should be left as spaces, apostrophes should be apostrophes, etc. No substitutions are needed for this URL.
Character name should also be unescaped. Case shouldn’t matter.
Data returned is in the general format:
‘guild’: null, // not populated at this time
date: ‘DATE’, // date is in milliseconds, see date notes in above feed
value: ‘VALUE’, // DPS or HPS value for this fight
duration: ‘VALUE’ // length of fight in milliseconds
// same as above, these are just older bosses that aren’t current
Spec IDs are inherited from how World of Logs identifies specs on their own site. Raidbots uses the same ID system. The simplest way to look at spec IDs is to check the source for one of my helper classes: