Endpoints

Retrieve Player’s Risk Profile

get
/v1/Operator/PlayerRiskProfile/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}/accountid/{accountId}

Fetches Risk Profile for a specific account ID under a given bookmaker and sub-bookmaker.

Path parameters
bookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 123
subBookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the sub-bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 456
accountIdstring · plain-text · min: 1 · max: 64Required

Account ID for which to retrieve data. Account ID should belong to the specified bookmaker and sub-bookmaker.

Example: player_1
Responses
200

Player risk profile retrieved

get
/v1/Operator/PlayerRiskProfile/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}/accountid/{accountId}

Retrieve All Players' Risk Profiles

get
/v1/Operator/RiskProfiles/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}

Retrieve the latest risk scores for player IDs associated with a specific bookmaker and sub-bookmaker ID. The results will be paginated, with a maximum of 1,000 players per page. The response can be limited to only players with risk score changes on or after the provided date.

Path parameters
bookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 123
subBookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the sub-bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 456
Query parameters
pageinteger · int32 · min: 1 · max: 2147483647Optional

The page number to retrieve. Starts at 1. Defaults to 1.

Example: 1
fromDateTimestring · date-timeOptional

Optional. Filters results to include only records on and after the specified date and time. Data is available for up to 30 days prior to the current date.

Format: ISO 8601 (e.g., YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ) Examples: Date only: 2024-12-24 Date + time: 2024-12-24T14:30:00Z (UTC) Date + time + offset: 2024-12-24T14:30:00+02:00

Example: 2024-12-24T00:00:00Z
Responses
200

OK

get
/v1/Operator/RiskProfiles/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}

Send Intervention Feedback

post
/v1/Operator/PlayerFeedback/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}

Send the intervention method used for the player associated with a specific bookmaker and sub-bookmaker ID along with the intervention dateTime.

Path parameters
bookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 123
subBookmakerIdinteger · int32 · max: 2147483647Required

Identifier for the sub-bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.

Example: 456
Query parameters
PlayerIdstring · plain-text · min: 1 · max: 64Required

Account ID of the player

InterventionMethodinteger · enum · min: 1 · max: 6Required

Enum values: 1 = DISPLAY_POP_UP, 2 = DISPLAY_RG_MESSAGING, 3 = EMAIL_PLAYER, 4 = DISPLAY_LIMITS_UPDATE, 5 = CARE_CALL, 6 = OTHER

Possible values:
InterventionDateTimestring · date-timeRequired

Timestamp when the intervention occurred. Format: ISO 8601 (e.g., YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ

Responses
200

OK

Responsestring · plain-text · max: 256
post
/v1/Operator/PlayerFeedback/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}

Last updated

Was this helpful?