Skip to main content
These are administrator-only endpoints. Require admin authentication.

​
Overview

The reporting endpoints allow administrators to:
  • View standing information for instances and players
  • Blacklist instances from leaderboards
  • Update player cheat levels
  • View flagged activities and players

​
Get Instance Standing

Retrieve detailed standing information for a specific instance, including flags, blacklist status, and per-player standing data.

​
Endpoint

GET /admin/reporting/standing/{instanceId}

​
Path Parameters

​
instanceId
string
required
The instance ID (int64 as string)

​
Response

​
instanceDetails
object
required
Basic instance information (see Instance schema in OpenAPI spec)
​
blacklist
object
Blacklist information if the instance is blacklisted, otherwise null
​
flags
array
required
Array of automated flags detected for this instance
​
players
array
required
Array of player standing information for this instance

​
Error Responses

​
404
object
Instance Not Found

​
Blacklist Instance

Blacklist or un-blacklist an instance from leaderboards, optionally blacklisting specific players.

​
Endpoint

PUT /admin/reporting/blacklist/{instanceId}

​
Path Parameters

​
instanceId
string
required
The instance ID to blacklist or un-blacklist

​
Request Body

​
reason
string
required
Reason for blacklisting (minimum 1 character)
​
reportId
integer
Associated report ID if applicable
​
removeBlacklist
boolean
default:"false"
If true, removes the blacklist instead of adding it
​
players
array
Optional array of players to blacklist with individual reasons

​
Response

​
blacklisted
boolean
required
true if instance was blacklisted, false if blacklist was removed

​
Example Request

{
  "reason": "Confirmed exploit usage",
  "reportId": 12345,
  "removeBlacklist": false,
  "players": [
    {
      "membershipId": "4611686018488107374",
      "reason": "Primary exploiter"
    }
  ]
}

​
Error Responses

​
400
object
Player Not In Instance - One or more specified players are not in this instance
​
404
object
Instance Not Found

​
Update Player

Update player fields, currently supporting cheat level modifications.

​
Endpoint

PATCH /admin/reporting/player/{membershipId}

​
Path Parameters

​
membershipId
string
required
The player’s membership ID (int64 as string)

​
Request Body

​
cheatLevel
integer
New cheat level for the player. One of:
  • 0: None
  • 1: Suspicious
  • 2: Moderate
  • 3: Extreme
  • 4: Blacklisted

​
Response

Returns a success message string: 
{
  "minted": "2024-03-03T23:30:00.000Z",
  "success": true,
  "response": "Player 'Newo#9010' updated successfully."
}

​
Error Responses

​
404
object
Player Not Found

​
Authentication

All reporting endpoints require admin JWT token: 
curl -X GET https://api.raidhub.io/admin/reporting/standing/12345678901234567 \
  -H "Authorization: Bearer YOUR_ADMIN_TOKEN"

​
Common Use Cases

  • Investigate Reports: Review flagged instances and player behavior
  • Moderate Leaderboards: Remove illegitimate clears from rankings
  • Track Cheaters: Monitor players with suspicious activity patterns
  • Manual Review: Override automated systems when necessary

Build docs developers (and LLMs) love

Get started for freeTalk to us