> 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/tournament-profiling-api/faqs.md).
# FAQs
### ❓ What is the Tournament Profiling API?
The Tournament Profiling API is part of Insight Tech Services and provides real-time tournament ratings and live time delay recommendations. These insights help operators manage risk by dynamically adjusting validation, stake limits, and cash-out logic across tournaments in over 100 sports.
### ❓ What does the Tournament Rating represent?
Each tournament is assigned a rating from 1 to 10, where:
* **1** = Highest risk (lowest limits)
* **10** = Lowest risk (highest limits)
The rating reflects:
* Expected turnover
* Market and coverage quality
* Betting volume
* Risk signals from MTS traders and predictive models
There are separate values for pre-match and live betting:
* `prematchTr` – rating for pre-match
* `liveTr` – rating for live markets
### ❓ What is Live Time Delay Settings?
The `liveTimeDelaySettings` provide recommended delay values (in seconds) applied during live betting based on coverage type:
* `liveTimeDelayTv` – when the event has TV coverage
* `liveTimeDelayUmpire` – when covered by an umpire
* `liveTimeDelayVenue` – when covered by a scout in the venue
These values help mitigate validation and liability issues in fast-changing markets.
### ❓ When should this API be used?
The API should be called proactively and periodically, especially:
* When ingesting or refreshing tournament/event data
* Ahead of matchdays competitions
* During regular configuration syncs
* As input into risk rule engines, stake factor tables, or cashout validation flows
### ❓ What are the required input parameters?
To call the API, you must supply:
* `bookmaker` – your assigned bookmaker ID
* `sportId` – ID of the sport
* `categoryId` – ID of the competition or region
The `POST` endpoint accepts multiple IDs for batch queries.
### ❓ What data is returned in the response?
Each item includes:
* `liveTr`: Tournament rating for live markets (1–10)
* `prematchTr`: Tournament rating for pre-match (1–10)
* `liveTimeDelaySettings`: Recommended delays for different coverage types
* `tournamentId`: Identifier for the tournament
Optional metadata may include risk notes or coverage indicators.
### ❓ How are tournament ratings calculated?
Ratings are calculated using:
* Weighted averages of ratings from upcoming events (within 2 weeks)
* Historical turnover expectations
* Trader-configured risk levels
* ML models trained on outcome volatility and market quality
Ratings are dynamically updated based on event data.
### ❓ How should operators use this API?
Operators can:
* Feed ratings into risk engines, stake factor matrices, or validation logic
* Map ratings into risk buckets (e.g. low-risk = 8–10, medium = 4–7, high = 1–3)
* Use delay settings to configure live bet validation windows
* Combine tournament ratings with player-level models (e.g. sCCF, LBS)
### ❓ Can the API handle multiple tournaments at once?
Yes.
* The `GET` endpoint supports querying a single sport/category
* The `POST` endpoint supports multiple tournaments for batch processing
### ❓ What are the API rate limits?
| Limit Type | Value |
| --------------- | ----------- |
| Requests/second | 1 |
| Minute quota | 15 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
### ❓ What happens if tournament data is not available?
If data is missing:
* The response may omit certain fields or return null
* Operators should fall back to default configuration
* Ratings can be retrieved later once event data is populated
### ❓ Who can I contact for support or access?
For access issues, integration help, or data questions, contact:
* Your OAM
* Your assigned CI engineer
* Or submit a ticket via Sportradar support.
---
# 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 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/tournament-profiling-api/faqs.md?ask=
```
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.