> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/itservices/models/customer-confidence-factor-ccf-api.md).

# Customer Confidence Factor (CCF)

<figure><img src="https://2001682152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYycr0Ox2VhGjrxN1zh9t%2Fuploads%2FVSWAU6hPjSHEAQB0QRPi%2Fbanner-feature-customer-confidence-factor.png?alt=media&amp;token=8c9b8e72-8a25-4ec6-8e21-650bae1c6565" alt=""><figcaption></figcaption></figure>

The Customer Confidence Factor (CCF) API OpenAPI specification is available for [download here.](https://sr-gitbook-prod-openapi.s3.eu-central-1.amazonaws.com/trading-and-risk-management/insight-tech-services/CCF-API-production-oas30.json)\
Explore the API [endpoints here.](https://docs.sportradar.com/itservices/models/customer-confidence-factor-ccf-api/endpoints.md)

The **Customer Confidence Factor (CCF)** API allows clients to retrieve the latest confidence score associated with each customer, shop, or terminal. This value plays a central role in managing risk across sportsbook operations, particularly when combined with automated or manual stake restrictions.

### What it does

The CCF represents a real-time grading of an account's trustworthiness or value, reflecting a bettor’s historical behaviour, risk profile, and betting pattern. It is used to calculate permitted stake levels and control exposure. CCFs are either assigned manually via the MTS Console or computed using the sCCF model and adjusted via Auto CCF logic.

### When it's triggered

Clients can call the API on demand to retrieve the latest CCF values. The data is available for individual entities or in batches. The API supports pagination and allows lookups by customer, shop, or terminal – either individually or in combination.

### Input requirements

Each request must specify the following identifiers:

* `bookmaker` – the assigned Insight Tech or MTS bookmaker ID
* `sub-bookmaker` – the sub-entity of the bookmaker (use `*` to retrieve all sub-entities)
* `customer`, `shop`, or `terminal` – depending on the selected endpoint

Some endpoints also support range filters (`lower`, `higher`) or pagination using `startKey`. A full breakdown of all accepted parameters is available in the [Endpoints](https://docs.sportradar.com/itservices/models/customer-confidence-factor-ccf-api/endpoints.md) section.

### Output schema

A typical response includes the list of items, and each object under `responseItem` contains:

* `srcId`: compound source identifier for internal tracking
* `ccf`: the current customer confidence score (a decimal number)
* `id`: entity identifier

### Interpretation guidance

The returned CCF values determine the allowed stake size and validation flow. Higher values (e.g. 1.2 and above) reflect trustworthy or high-value accounts, while lower values (e.g. below 0.8) indicate accounts under scrutiny or severe restriction.

Auto CCF logic automatically adjusts CCFs based on model outputs (sCCF), within configured limits and rules. Manual overrides are respected, and analysts can disable automation for specific accounts.

The colour-coded CCF groups in the Console (e.g. red for low, green for high) provide quick context when reviewing tickets and accounts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/itservices/models/customer-confidence-factor-ccf-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
