# FAQs

<figure><img src="/files/Tygvy3qu5wzIzgNnXdtq" alt=""><figcaption></figcaption></figure>

### ❓ What is the Player Profiling API?

The Player Profiling API provides a real-time, consolidated risk profile of a customer using multiple behavioural and machine learning models. It helps operators make informed decisions about validation, delays, bonuses, and responsible gaming interventions.

### ❓ When should I use the Player Profiling API?

Use the API:

* At the moment of ticket or cashout placement
* When applying risk-based delays or bonuses
* As part of automated trading strategies, alerting systems, or CRM segmentation

### ❓ What input parameters are required?

You need to provide:

* `bookmaker`: Your assigned Insight Tech or MTS bookmaker ID
* `sub-bookmaker`: Optional, used for multi-tenant clients
* `account`: The customer’s unique account ID

These identifiers ensure the API retrieves the latest scores for the correct user.

### ❓ What kind of scores does the API return?

The API returns the following fields:

* *Suggested Customer Confidence Factor*: A model-generated confidence score used in Insight Tech workflows
* *Customer Confidence Factor*: The score currently active in MTS validation
* *Bot Score*: Probability the account is a bot or using scripts
* *Late Bet Score*: Indicates whether a user tends to bet close to in-game events
* *Marker Score*: Flags sharp, problematic, or high-risk behaviour patterns

### ❓ What is the difference between `sccf` and `ccf`?

* `sccf` is calculated by a machine learning model for use in custom workflows and decision engines (Insight Tech).
* `ccf` is the operational score applied by MTS in real-time ticket validation.

If you're using MTS, `ccf` should be enforced. If you're using Insight Tech or hybrid mode, you can apply `sccf` via your own logic.

### ❓ What is a good or bad value for these scores?

There are no fixed thresholds. Each score is designed to be interpreted relative to your customer base. However:

* High `sccf` / `ccf`: Trusted user
* Low `sccf` / `ccf`: Risky user (consider applying delay, limits, or additional checks)
* High `botScore`: Likely automation
* High `lbs`: Risk of timing abuse
* High `markerScore`: Sharp or high-risk activity

Operators are encouraged to define internal rules and thresholds based on historical benchmarks.

### ❓ How frequently are these scores updated?

The models are updated:

* CCF: In real-time or near real-time (e.g. after a new bet or change in player behaviour)
* other factors: Daily, based on recent signals (e.g. betting patterns, stakes, speed)

You should query this API just-in-time during validation workflows or as part of scheduled jobs.

### ❓ What does the `accountType` mean?

* `C` – Customer (end user)
* `S` – Shop
* `T` – Terminal

Most scoring applies to `C` type accounts.

### ❓ What happens if no scores are available?

If a new or inactive user has no available scores:

* The API may return nulls or empty values
* Fallback logic (e.g. apply default delay or block high-stake bets) should be implemented

*Note: CCF value should always be present for existing bettors.*

### ❓ How should I combine these scores with other APIs?

You can combine Player Profiling with:

* Live Time Delay (LTD) API to decide whether to skip/apply delay
* Event Profiling / Tournament Profiling APIs to assess event-level risk
* Cashout validation engines to enhance decision confidence
* CRM tools or compliance platforms to trigger alerts or workflows

### ❓ Are there rate limits?

| Limit Type      | Value            |
| --------------- | ---------------- |
| Requests/second | 10               |
| Daily quota     | 200,000 requests |
| Minute quota    | 500 requests     |

If you exceed the rate limit:

* You will receive `HTTP 429 Too Many Requests`
* Use exponential backoff for retries
* Keep request volumes efficient and cache results when possible

### ❓ Who can help me integrate this API?

For access issues, integration help, or data questions, contact:

* Your OAM
* Your assigned CI engineer
* Or submit a ticket via Sportradar support.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sportradar.com/itservices/models/player-profiling-api/faqs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.