Skip to main content
GET
/
metrics
/
population
/
rolling-day
curl --request GET \
  --url 'https://api.raidhub.io/metrics/population/rolling-day' \
  --header 'X-API-Key: your_api_key'

{
  "minted": "2026-03-03T23:30:00.000Z",
  "success": true,
  "response": [
    {
      "hour": "2026-03-03T23:00:00.000Z",
      "population": {
        "1": 342,
        "2": 156,
        "3": 89,
        "4": 234,
        "5": 167,
        "6": 201,
        "7": 445,
        "8": 312,
        "9": 523,
        "10": 678
      }
    },
    {
      "hour": "2026-03-03T22:00:00.000Z",
      "population": {
        "1": 389,
        "2": 178,
        "3": 92,
        "4": 267,
        "5": 189,
        "6": 223,
        "7": 478,
        "8": 334,
        "9": 556,
        "10": 701
      }
    },
    {
      "hour": "2026-03-03T21:00:00.000Z",
      "population": {
        "1": 412,
        "2": 201,
        "3": 103,
        "4": 289,
        "5": 198,
        "6": 245,
        "7": 501,
        "8": 367,
        "9": 589,
        "10": 734
      }
    }
  ]
}

​
Overview

This endpoint returns player activity metrics for each raid, aggregated by hour over the past 24 hours. Use this data to track player engagement trends and identify peak activity times across different raid activities.

​
Response

The response is an array of hourly snapshots, each containing the timestamp and population data for all raid activities.
​
response
array
Array of hourly population snapshots

​
What Metrics Are Tracked

The population metrics track player activity across all raid activities:
  • Player Count: Number of unique players who participated in each raid activity during the hour
  • Hourly Aggregation: Data is grouped by hour, providing a rolling 24-hour view
  • Activity Breakdown: Population is tracked separately for each raid activity ID
The data helps identify:
  • Which raids are most active at different times
  • Peak activity hours for raid participation
  • Trends in player engagement over the day

​
Response Structure

The population data is returned as a map (object) where:
  • Keys: Raid activity IDs (integers stored as strings in JSON)
  • Values: Total player count for that activity during the hour
To get human-readable raid names, map the activity IDs using the activity definitions from the manifest endpoint. 
curl --request GET \
  --url 'https://api.raidhub.io/metrics/population/rolling-day' \
  --header 'X-API-Key: your_api_key'

{
  "minted": "2026-03-03T23:30:00.000Z",
  "success": true,
  "response": [
    {
      "hour": "2026-03-03T23:00:00.000Z",
      "population": {
        "1": 342,
        "2": 156,
        "3": 89,
        "4": 234,
        "5": 167,
        "6": 201,
        "7": 445,
        "8": 312,
        "9": 523,
        "10": 678
      }
    },
    {
      "hour": "2026-03-03T22:00:00.000Z",
      "population": {
        "1": 389,
        "2": 178,
        "3": 92,
        "4": 267,
        "5": 189,
        "6": 223,
        "7": 478,
        "8": 334,
        "9": 556,
        "10": 701
      }
    },
    {
      "hour": "2026-03-03T21:00:00.000Z",
      "population": {
        "1": 412,
        "2": 201,
        "3": 103,
        "4": 289,
        "5": 198,
        "6": 245,
        "7": 501,
        "8": 367,
        "9": 589,
        "10": 734
      }
    }
  ]
}

​
Activity ID Mapping

Activity IDs correspond to different raid activities. Some common examples:
  • 1: Leviathan
  • 2: Eater of Worlds
  • 3: Spire of Stars
  • 4: Last Wish
  • 7: Garden of Salvation
  • 9: Vault of Glass
  • 10: Deep Stone Crypt
For a complete and up-to-date mapping, use the /manifest endpoint to retrieve all activity definitions with their IDs and names.

​
Notes

  • Response is cached for 5 minutes
  • Data covers a rolling 24-hour period from the current hour
  • Population counts represent unique players per activity per hour
  • Hours are in UTC timezone
  • Only includes raid activities (dungeons and other activity types are not included)

Build docs developers (and LLMs) love

Get started for freeTalk to us