API overview

The API lets you read detections, players and servers programmatically.

Base URL

https://web.thorium.ac

Authentication

Create a key under Networks → your network → API Keys, then send it as a bearer token:

curl -H "Authorization: Bearer $THORIUM_API_KEY" \
  "https://web.thorium.ac/api/players/paginated?orgId=$ORG_ID&page=1&pageSize=50"

A key is scoped to the network that issued it. Creating and revoking keys requires the relevant permission — see members and roles.

Caution

An API key can read your network’s player and detection data. Store it as a secret, never in client-side code, and revoke it in the dashboard if exposed.

Paging

List endpoints take page and pageSize (max 100) and return a pagination object with totalPages, hasNextPage and hasPreviousPage.

Common endpoints

Method	Path	Returns
GET	/api/players/paginated	Players, newest activity first
GET	/api/players/paginated/detections	Detections for the network
GET	/api/players/{id}	One player with recent detections
GET	/api/servers?organizationId=	Servers and connection state
GET	/api/organizations/{id}/entitlement	Plan, trial state, server allowance

Errors

Status	Meaning
401	Missing or invalid key
403	The key’s role lacks the permission
402	The plan does not permit the action — for example adding a server past the allowance
429	Rate limited. Retry-After says when to try again