Gains leaderboards
The guild page’s gains leaderboards over the accounts whose stats the key may read: the top 10 per skill. Default period=day.
Authorization
bearerAuth An API key from the hub’s API keys page.
In: header
Query Parameters
One skill, case-insensitive (overall works). Without it: Overall first, then every skill anyone gained XP in.
1 <= lengthday = since local midnight in the key creator’s time zone; week/month = the last 7/30 days. Default day.
Value in
- "day"
- "week"
- "month"
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/leaderboards/gains"{ "data": { "period": "day", "from": "2019-08-24T14:15:22Z", "to": "2019-08-24T14:15:22Z", "leaderboards": [ { "skill": "string", "entries": [ { "rank": 1, "account": { "id": "string", "name": "string" }, "gain": 0 } ] } ] }, "meta": { "generated_at": "2019-08-24T14:15:22Z" }}Location trails of several accounts GET
The location trails of several accounts in one call, in request order (`location_history`): up to 10 accounts with a user key, 50 with a service key, each trail exactly what `/accounts/{id}/locations` returns for the same range (at most one point per minute, oldest first, kept 30 days). An account the key can’t read makes the whole request 404. Default: the last 30 days.
Loot leaderboard GET
The period’s most valuable drops over the accounts whose `events` the key may read: `loot` and `pk_loot` events with a value, not on a special world, highest `value_gp` first. Each entry’s `event` is exactly what `/events` serves (with `data.location` removed the same way), though it can appear here a few seconds before the `/events` cursor serves it. Default `period=day`, `limit=10` (at most 50).