Server integration

There are two, and picking the right one is the most consequential decision in this integration.

A community whose reports stopped counting still keeps its own servers protected: its bans remain in ADVISORY, so it can consume its own data. Losing scoring weight limits a community’s effect on everyone else, not its ability to run its own ban list.

GET https://api.wardogs.social/api/v1/banlist

Query parameters, all optional:

A response row looks like this:

{
  "steamId64": "76561198000000001",
  "personaName": "example",
  "reputationScore": 12.5,
  "acceptedReports": 3,
  "offenseCodes": ["CHEATING", "TEAM_KILLING"],
  "lastAcceptedAt": "2026-09-01T18:22:04Z"
}

Treat steamId64 as a string. A SteamID64 is 17 digits, which exceeds the largest integer JavaScript can represent exactly — parsing one as a number silently rewrites the last digits and gives you a different account. In a ban list that means banning the wrong person. Most JSON parsers do this by default; use a string or big-integer parser.

The feed returns an ETag. Send it back as If-None-Match and an unchanged feed answers 304 Not Modified with no body, so polling every minute costs almost nothing.

# first call - note the ETag
curl -sS -D - -o banlist.json \
  "https://api.wardogs.social/api/v1/banlist?feed=TRUSTED"

# subsequent calls - 304 when nothing changed
curl -sS -o banlist.json \
  -H 'If-None-Match: "<etag from above>"' \
  "https://api.wardogs.social/api/v1/banlist?feed=TRUSTED"

The ETag covers the feed and minReports, so change either and you get a fresh response rather than a stale 304.

Every report carries one of these. The objective ones are matters of fact rather than judgement, so they count from any community regardless of its trust tier — that is what stops a brand-new community being unable to report someone destroying their own team’s vehicles.

The catalogue couldn’t be loaded. Fetch https://api.wardogs.social/api/v1/offense-types directly for the current list.

Reading the banlist needs no key — it is public data, and keeping it open means a server can protect itself before it has registered anything. A key is required only to submit reports programmatically, because that writes to other people’s reputations.

POST https://api.wardogs.social/api/v1/reports
X-Wardogs-Api-Key: <your key>
Content-Type: application/json

A key authenticates as your community. Anything submitted with it lands in your accepted-ban rate and therefore in your trust tier, so keep it on the server and out of client-side mods and public repos. Keys are issued and revoked per community; revoking one takes effect immediately.

Key management lives in the community settings screen, which is not built yet. Until it is, ask a platform admin to issue one.