Player Reports Web APIs

Use the Player Reports Web APIs to use Player Reports interface features with RESTful services.

5 mins to read

API Endpoint

Sending new player reports


The client policy used must have either one of these permissions:

  • playerreports:sendReportForAnyUser: When the client has permission to send reports on behalf of any player. Typically when the reports are coming from a game server.


This call requires Bearer Token authorization with an EOS Client Auth access token, obtained from the Connect interface.


HTTP Request POST /player-reports/v1/report
HTTP Headers
Content-Type application/json
Request Body
reportingPlayerId String The EOS productUserId making the report Yes
reportedPlayerId String The reported EOS productUserId. It must be different from the “reportingPlayerId”. Yes
time String

Time when the report was issued as defined in ISO 8601 and RFC3339. example: 2021-01-01T00:00:00.000Z

reasonId Integer

The report reason ID. It must be a valid ID. Refer to


API endpoint for more information

message String The report message with a maximum length of 1024 characters No
context String

Any valid Json. For any relevant information deemed useful for the developers. It has a maximum length of 4096 characters


Example Request

curl --location --request POST '' \
--header 'Content-Type: text/plain' \
--data-raw '{
"time": "2020-04-02T00:00:00.000Z",
"reportingPlayerId": "player_1",
"reportedPlayerId": "player_2",
"reasonId": 1,
"message":"This player is cheating",
"context" : "{\"key\": \"value\"}"


HTTP Response 201 - CREATED: Success.

Find Player Reports