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

https://api.epicgames.dev/player-reports/v1/report

Sending new player reports

Policy

The client policy used must have the following permission:

  • 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.

Authorization

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

Request

HTTP RequestPOST /player-reports/v1/report
HTTP Headers
NameValue
Content-Typeapplication/json
Request Body
NameTypeDescriptionRequired
reportingPlayerIdStringThe EOS productUserId making the reportYes
reportedPlayerIdStringThe reported EOS productUserId. It must be different from the reportingPlayerId.Yes
timeString

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

Yes
reasonIdInteger

The report reason ID. It must be a valid ID. Refer to /player-reports/v1/report/reason/definition API endpoint for more information

Yes
messageStringThe report message with a maximum length of 1024 charactersNo
contextString

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

No

Example Request

Response

HTTP Response 201 - CREATED: Success.

Find Player Reports

Policy

The client policy used must have the following permission:

  • playerreports:findReportsForAnyUser: When the client has permission to get reports for any players.

Authorization

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

Request

HTTP RequestGET /player-reports/v1/report/{deploymentId}
Request Parameters
NameTypeDescriptionRequired
deploymentIdStringThe EOS deploymentId. It has to match the deploymentId generated by the access tokenYes
reportingPlayerIdStringThe EOS productUserId making the report. reportingPlayerId and reportedPlayerId cannot both be emptyNo
reportedPlayerIdStringThe reported EOS productUserId. reportingPlayerId and reportedPlayerId cannot both be emptyNo
reasonIdInteger

The report reason Id. It must be a valid id. Refer to

/player-reports/v1/report/reason/definition

API endpoint for more information

No
startTimeString

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

No
endTimeString

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

No
paginationBoolean

Enable/Disable pagination response. Default value : false

No
offsetInteger

The pagination offset Default value: 0

No
limitInteger

The reports count returned per call Default value: 50

No
orderString

The order followed by returned reports: Possible values:

  • time:desc
  • time:asc
  • reasonId:asc
  • reasonId:desc

Default value: time:desc

No

Example Request

Response

HTTP Response 200 - OK: Success.
HTTP Headers
NameValue
Content-Typeapplication/json
JSON Payload
NameTypeDescription
elementsArray<Report>List of reports
paging

Object<Paging>

Pagination information

Paging

Paging
NameTypeDescription
offsetIntegerThe pagination offset
limitIntegerThe reports count returned per call
totalIntegerThe total reports count

Report

Report
NameTypeDescription
productIdStringThe game EOS productId
sandboxIdStringThe game EOS sandboxId
deploymentIdStringThe game EOS deploymentId
timeString

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

reportingPlayerIdStringThe EOS productUserId making the report
reportedPlayerIdStringThe reported EOS productUserId
reasonIdIntegerThe report reasonId
messageStringThe report content
contextStringThe report context

Example Response

Get Report Reason Definition

Policy

No special client permissions are needed to call the report definition API

Authorization

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

Request

HTTP RequestGET /player-reports/v1/report/reason/definition

Example Request

Response

HTTP Response 200 - OK: Success.
HTTP Headers
NameValue
Content-Typeapplication/json
JSON Payload
NameTypeDescription
elementsArray<ReportReason>List of report reasons

ReportReason

ReportReason
NameTypeDescription
reasonIdIntegerThe report reason Id
reasonStringStringA String describing the reasonId

Example Response