Endpoints
Fetches Risk Profile for a specific account ID under a given bookmaker and sub-bookmaker.
Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.
123
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.
456
Account ID for which to retrieve data. Account ID should belong to the specified bookmaker and sub-bookmaker.
player_1
Player risk profile retrieved
Player not found
Player profile not created
Player profile is inactive
Internal Server Error
GET /rg/api/v1/Operator/PlayerRiskProfile/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}/accountid/{accountId} HTTP/1.1
Host: api.insighttechservices.sportradar.com
Accept: */*
{
"playerId": "player_1",
"lastUpdatedDateTime": "2025-07-01T00:14:00Z",
"riskScore": 54,
"riskCategory": 1,
"percentile": 46.840744,
"categoryScores": [
{
"key": 3,
"name": "Losses",
"score": 3.7177
},
{
"key": 2,
"name": "Depositing behaviour",
"score": 0.99289995
},
{
"key": 5,
"name": "Speed of play",
"score": 0.7379
},
{
"key": 6,
"name": "Withdrawal-related behaviour",
"score": 0.3308
},
{
"key": 8,
"name": "RG activity",
"score": -0.1552
},
{
"key": 4,
"name": "Time",
"score": -1.0741
},
{
"key": 1,
"name": "Betting behaviour",
"score": -4.0785
}
]
}
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.
Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.
123
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.
456
The page number to retrieve. Starts at 1. Defaults to 1.
1
Optional. Filters results to include only records on and after this date and time.
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
2024-12-24T00:00:00Z
OK
Invalid page parameter
Not Found
Internal Server Error
GET /rg/api/v1/Operator/RiskProfiles/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId} HTTP/1.1
Host: api.insighttechservices.sportradar.com
Accept: */*
{
"items": [
{
"playerId": "player_1",
"lastUpdatedDateTime": "2025-07-01T00:00:00Z",
"riskScore": 2,
"riskCategory": 0,
"percentile": 99.12692
},
{
"playerId": "player_2",
"lastUpdatedDateTime": "2025-07-01T00:00:00Z",
"riskScore": 71,
"riskCategory": 2,
"percentile": 32.49798
}
],
"page": 1,
"pageSize": 1000,
"totalCount": 2,
"hasPreviousPage": false,
"hasNextPage": false
}
Send the intervention method used for the player associated with a specific bookmaker and sub-bookmaker ID along with the intervention dateTime.
Identifier for the bookmaker. Generated by Sportradar, contact your account manager or CI engineer in case of any issues with obtaining the correct value.
123
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.
456
Account ID of the player
Enum values: 1 = DISPLAY_POP_UP, 2 = DISPLAY_RG_MESSAGING, 3 = EMAIL_PLAYER, 4 = DISPLAY_LIMITS_UPDATE, 5 = CARE_CALL, 6 = OTHER
Timestamp when the intervention occurred. Format: ISO 8601 (e.g., YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ
OK
Bad Request
Conflict
Internal Server Error
POST /rg/api/v1/Operator/PlayerFeedback/bookmakers/{bookmakerId}/sub-bookmakers/{subBookmakerId}?PlayerId=text&InterventionMethod=1&InterventionDateTime=2025-10-03T12%3A34%3A27.254Z HTTP/1.1
Host: api.insighttechservices.sportradar.com
Accept: */*
text
Was this helpful?