Tracker data - API reference - Entropia Central

Everything Entropia Central records from tracked play is readable over a plain REST API. Globals, HOFs and ATHs, the 24 hour summaries behind the site's own dashboards, and the leaderboard standings are all public and need no credentials.

These endpoints are read-only. For a live push feed rather than polling, see SignalR hubs.

All paths below are relative to https://api.entropiacentral.com.

Listing globals

http

GET /globals

Returns a paginated, filtered list. Every parameter is optional.

Parameter	Type	Notes
`type`	string	Hunting, Mining, Space Mining, Construction, Discovery, Rare Item, Tiered Item or PvP
`creatureName`	string	Filter by creature
`creatureId`	number	Filter by wiki creature id
`isHof`, `isAth`, `isTeam`	boolean	Classification filters
`minValue`, `maxValue`	number	Value range in PED
`fromDate`, `toDate`	date	Time range
`search`	string	Full text search across the original message, so it matches avatars, creatures, items and deposits
`sortBy`	string	`DateTime`, `GlobalValue`, `AvatarName` or `Type`. Defaults to `DateTime`
`sortOrder`	string	`asc` or `desc`. Defaults to `desc`
`pageNumber`	number	Defaults to 1
`pageSize`	number	Defaults to 10, maximum 30

Anything outside those bounds returns 400, including a minValue above maxValue, a fromDate after toDate, or a sortBy outside the four accepted fields. The API does not silently clamp, so validate before you send.

bash

curl "https://api.entropiacentral.com/globals?type=Hunting&minValue=1000&pageSize=30"

Recent globals

http

GET /globals/recent?count=50

count accepts 1 to 200 and defaults to 50. This reads from cache and falls back to the database, so it is the cheaper option when you just want the latest activity rather than a filtered query.

http

GET /globals/last-5

A fixed-size version of the same feed intended for compact widgets. Note it currently returns seven entries despite the name, so read the length rather than assuming five.

Twenty-four hour summaries

http

GET /globals/top-24h?excludeTeams=false

The top 10 globals by value for each profession over the last 24 hours: hunting, mining, space mining, construction and PvP sprees. excludeTeams only affects hunting and space mining. Cached for five minutes.

http

GET /globals/activity-24h

Hourly counts over the last 24 hours broken down by profession, one bucket per hour with gaps filled as zero, so it can be charted directly without post-processing. Cached for 60 seconds.

Inspecting one global in context

http

GET /globals/inspect/{id}

Returns a single global plus up to 20 globals either side of it chronologically. Useful for verifying a record or seeing what surrounded it. Returns 404 if the id does not exist.

Leaderboards

http

GET /leaderboard/overall
GET /leaderboard/hunting
GET /leaderboard/mining
GET /leaderboard/space-mining
GET /leaderboard/construction
GET /leaderboard/pvp

Each accepts page (defaults to 1) and an optional search to find a specific avatar.

How points are earned

Standings cover a rolling three month window and exclude team globals entirely.

Activity	Points
Hunting global worth 50 PED or more	6
Hunting global under 50 PED	3
Mining global	6
Space mining global	6
Construction global	6
PvP, per kill in a spree	2
PvP, per recorded kill action	0.5
Rare item	0.5
Tiering	5
Discovery	50

Two things follow from this that are not obvious. Mining, space mining and construction globals score a flat 6 regardless of value, so a 40 PED mining claim is worth the same as a 4,000 PED one, while hunting is the only profession with a value threshold. And a single discovery is worth 50 points, more than eight hunting globals, which is why a discovery can move an avatar up the standings overnight.

Leaderboards are rebuilt by a scheduled job rather than on write, so a global will appear in the feeds before it is reflected in the standings.

Notes for polling

Prefer /globals/recent over a filtered /globals query when you are polling, since it is cache-backed. If you need every record as it happens rather than on an interval, use the globals hub instead of polling at all.

Page size on /globals is capped at 30, so pulling a large history means many requests. Filter by date range and walk backwards rather than paging deep into an unfiltered list.