FAQs

❓ What is the Late Bet Score API?

The Late Bet Score (LBS) API is a machine-learning solution from Sportradar's Insight Tech Services, designed to help operators detect accounts potentially engaging in late-bet abuse during live betting. It scores each customer account based on the likelihood of exploiting market latency to gain an unfair advantage.

❓ How does the LBS model work?

The model analyses betting behaviour across live single bets, looking for timing anomalies, sudden value spikes, and patterns that suggest market-aware latency abuse. A score between 0.00 and 1.00 is returned, where higher values indicate a stronger likelihood of late betting.

❓ What data is required to use the LBS API?

To query the API, you need the following:

• bookmaker: Insight Tech / MTS-assigned bookmaker ID

• sub-bookmaker: Specific entity under the bookmaker (or * for all)

• customer: The unique ID of the customer Endpoints also support score filters and pagination via startKey or lastEvaluatedKey.

❓ How often are scores calculated?

The Late Bet Score is calculated once daily. Each day, the model profiles accounts that placed at least one live single bet the previous day. Scores remain available via API until the next recalculation.

❓ What does a high score mean?

• Scores ≥ 0.90: Strong likelihood of late-bet abuse. These accounts are ideal candidates for increased Live Time Delay.

• Scores 0.70 – 0.89: Moderate risk. Behaviour warrants monitoring or conditional delay settings.

• Scores < 0.70: Reflect typical, non-suspicious betting behaviour.

❓ What happens if an account doesn’t have a score?

An account may not have a score if:

• It’s new and hasn’t placed relevant bets.

• It has been inactive, with no live single bets in the last profiling window.

• There’s insufficient data to make a reliable prediction.

❓ Can I use LBS scores to adjust live time delay automatically?

Yes. Operators commonly use LBS thresholds to:

• Assign dynamic Live Time Delay (LTD) values

• Enforce delay offset logic for high-risk accounts

• Escalate certain accounts for manual review

❓ What are the rate limits for the API?

To ensure stability, the API enforces the following limits:

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

Exceeding these will result in a 429 Too Many Requests response.

❓ How can I handle rate limiting in my integration?

Use exponential backoff strategies in your API client. After a rate-limited response, increase the retry interval gradually to avoid further throttling.

❓ Is real-time alerting supported?

The LBS API is currently pull-based, meaning scores must be fetched periodically. However, real-time alerting is being explored for future release and may be included as part of the Alerting UI.

❓ Can I adjust my usage quotas?

Yes. Quotas are based on your contract and expected volume. Contact your Sportradar account manager to request changes.

❓ Who should I contact for support?

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

• Your OAM

• Your assigned CI engineer

• Or submit a ticket via Sportradar support.