GET
/api/v1/live-tracking/guild/boss-attempts
Retrieve a simplified timeline of boss attempts with health percentages. Ideal for rendering progress over time charts and stream overlays.
Relies on combat log data retrieved from the Raider.IO Desktop App. Returns a simplified view compared to boss pulls — one entry per attempt with just the health percent and duration, ideal for charting.
Параметры
access_key
query
raid
query
required
boss
query
required
difficulty
query
required
region
query
required
realm
query
required
guild
query
required
period
query
GET
/api/v1/live-tracking/guild/boss-progress
Retrieve a guild's best progress on a specific boss, including best health percentage, total pull count, and kill status. Ideal for progress widgets and stream overlays.
Relies on combat log data retrieved from the Raider.IO Desktop App.
This is the most commonly used endpoint for stream overlays and progress widgets. Returns a single summary object rather than per pull detail.
Identify the guild using eith...
Параметры
access_key
query
raid
query
required
boss
query
required
difficulty
query
required
period
query
guild_id
query
region
query
realm
query
GET
/api/v1/live-tracking/guild/boss-pulls
Retrieve detailed pull history for a specific boss including wipe/kill status, health percentages, and duration. Supports filtering by lockout period and date range.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Health percentages and pull details may be hidden if the guild has restricted data via privacy settings — check the guildPrivacy and error fields in the response.
Параметры
access_key
query
raid
query
required
boss
query
required
difficulty
query
required
region
query
required
realm
query
required
guild
query
required
period
query
GET
/api/v1/live-tracking/guild/loot
Retrieve recent loot drops for a guild from combat log data. Filterable by time range and item type.
Relies on combat log data retrieved from the Raider.IO Desktop App.
By default returns items from the last 10 minutes. Use start time / end time for an explicit window, or duration minutes to adjust the look back period.
Параметры
access_key
query
raid
query
required
region
query
required
realm
query
required
guild
query
required
duration_minutes
query
start_time
query
end_time
query
GET
/api/v1/live-tracking/guild/raid-comps
Retrieve raid composition details for a specific pull, including the full roster with character specs, gear, and talents.
Relies on combat log data retrieved from the Raider.IO Desktop App.
You can look up a specific pull by id (obtained from the raid pulls endpoint), or omit it to get the latest pull. Identify the guild using either guild id or the region / r...
Параметры
access_key
query
raid
query
required
difficulty
query
id
query
guild_id
query
region
query
realm
query
boss
query
GET
/api/v1/live-tracking/guild/raid-progress
Retrieve overall raid progress for a guild across all bosses. Returns best percent, pull count, and kill status for every encounter in the raid.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Returns progress for all bosses in a single call — use this instead of calling boss progress once per boss.
Identify the guild using either guild id or the region / realm /...
Параметры
access_key
query
raid
query
required
difficulty
query
required
guild_id
query
region
query
realm
query
guild
query
period
query
GET
/api/v1/live-tracking/guild/raid-pulls
Retrieve pull counts and details for each boss encounter. Returns all encounters with pull history for the specified guild, raid, and difficulty.
Relies on combat log data retrieved from the Raider.IO Desktop App. Guilds that do not use the Desktop App will return empty results.
Identify the guild using either guild id or the region / realm / guild combination — do not mix both.
Параметры
access_key
query
raid
query
required
difficulty
query
required
period
query
start_range
query
end_range
query
region
query
realm
query
GET
/api/v1/live-tracking/raiding/bot-commands/{cmd}
Return a pre formatted string for use in Twitch/Discord bot commands. Supports template variables ($PCT, $BOSS, $PULL, $DIFFICULTY) for custom formatting.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Returns a plain text string (not JSON). Use the template parameter to customize the output format with variables: $PCT (best percent), $BOSS (boss name), $PULL (pull count)...
Параметры
cmd
path
required
access_key
query
raid
query
required
boss
query
required
difficulty
query
required
period
query
guild_id
query
region
query
Ответы
200
Formatted bot command response string
GET
/api/v1/live-tracking/rwf-event/feed
Retrieve a Race to World First event feed (kills, best percents, new pulls) for tracked guilds. Supports real time polling via the "after" cursor parameter.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Polling workflow: Call rwf event/last to get the starting cursor ID Call this endpoint with that ID as after and your guild ids On each poll, use the highest id from the re...
Параметры
access_key
query
raid
query
required
difficulty
query
required
types
query
guild_ids
query
required
border_style
query
after
query
required
test
query
GET
/api/v1/live-tracking/rwf-event/last
Retrieve the latest event ID for a Race to World First raid. Use the returned ID as the "after" cursor in the feed endpoint to poll for new events.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Polling workflow: Call this endpoint once to get the latest event ID, then pass it as the after parameter to the rwf event/feed endpoint. On each subsequent poll, use the h...
Параметры
access_key
query
raid
query
required
GET
/api/v1/live-tracking/user/activities/raiding
Retrieve raiding combat log contribution activities for a user in a given raid.
Relies on combat log data retrieved from the Raider.IO Desktop App.
Параметры
access_key
query
raid
query
required
user_id
query
required
types
query
required
GET
/api/v1/live-tracking/user/activity/raiding
Retrieve detailed information about a specific raid encounter from combat log data.
Relies on combat log data retrieved from the Raider.IO Desktop App. The response shape is similar to the /guilds/boss kill endpoint but sourced from combat log data rather than the Blizzard API.
Параметры
access_key
query
raid
query
required
encounter_id
query
required