API documentation
Live competition data, independent server feeds and EvoSC integration.
Public endpoints
Read endpoints require no API key. Live v1 responses use { ok, data, meta }; errors include a code and message.
/api/v1/healthBridge health and current API revision.
/api/v1/war/networkAll connected server streams with their current War.
/api/v1/war/active?server=primaryTeams, players, maps and scores for the selected server.
/api/v1/war/active/revision?server=primaryLightweight revision check for that server.
/api/v1/wars?server=primaryWar history for the selected server.
/api/v1/players/:login/profilePlayer identity, profile and badges.
/api/serversPublic community server registry.
/api/upcoming-warUpcoming event and authoritative registration counters.
/api/v1/ingest/warAuthenticated EvoSC snapshot ingest. Use the supplied WarApiBridge module.
Multiple simultaneous Wars
The main server and all three rental slots can publish at the same time. Select a serverId from the network endpoint and pass it as ?server=…. Revisions and War IDs belong to that server, not to the entire network. Keep the server ID with links to scores, maps and history.
fetch("/api/v1/war/network")
.then(response => response.json())
.then(({ data }) => console.log(data));Existing player career badges and the console-invite queue remain attached to the primary competition; other server streams do not consume its invite requests.
Connect EvoSC
- Register your community server and keep the returned server ID and one-time API key private.
- Install the supplied WarApiBridge module on your EvoSC controller.
- Set its endpoint to
https://wargrid.de/api/v1/ingest/war, plus its server ID and server key, then enable it. - Check the latest received snapshot in your server profile. Managed rentals configure their bridge automatically on first start.
The module signs requests using HMAC-SHA256 and supplies the timestamp, unique request ID, server identity and signature. Do not place server keys, admin keys or Node-agent tokens in browser code.
Explore server network