# FAQs

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

### **❓** What is the Live Time Delay (LTD) API?

The Live Time Delay (LTD) API is an AI-powered service that provides real-time recommendations for whether to apply, skip, or increase the live time delay for a ticket placement. It helps sportsbooks reduce risk exposure by making latency decisions at the exact moment of bet placement.

### ❓ What are the main use cases for the LTD API?

* Optimising latency per ticket based on customer trust level
* Skipping delays for low-risk users to improve experience
* Enforcing increased delay for suspicious or high-risk bets
* Integrating AI logic directly into bet placement validation

### ❓ What is `ltdModelSuggestion`?

This is the core output of the LTD API:

* `"Skip"` – Apply no delay (typically for trusted users)
* `"Delay"` – Apply standard or increased LTD
* `"N/A"` – No recommendation available (fallback to defaults)

Use this field to determine how to treat the live ticket in real time.

### ❓ How do `ltdSuggestion` and `ltdSuggestionEdl` differ?

* `ltdSuggestion`: Player-specific recommendation based on profiling (e.g. Late Bet Score, Confidence Score)
* `ltdSuggestionEdl`: Event-level recommendation based on the EDL model

You can:

* Prioritise one over the other
* Use the higher value for added safety
* Merge both into custom delay logic

### ❓ What triggers the LTD API?

The API is called:

* At the moment of ticket placement for live sports
* Only for live bets, not pre-match
* For sports and eSports covered by MTS or Insight Tech Services

### ❓ What are the input requirements?

The LTD API accepts the Ticket 3.0 schema. It supports:

* `ticket-placement`
* `ticket-inform`

You must also include:

* The full payload of the ticket
* Bookmaker identifier as a path parameter

### ❓ What if the suggestion is to skip the delay?

If `ltdModelSuggestion = "Skip"`, and your business rules allow it, you may:

* Accept the bet without LTD
* Prioritise faster user experience
* Reserve delay application for riskier users

*Note: This should only apply to users with high trust scores and low estimated margin loss (EML).*

### ❓ Are there cases where LTD is always enforced?

Yes. Delay is automatically recommended or enforced when:

* Players have low Confidence Scores or high Late Bet Scores
* The account is new with insufficient history
* The ticket involves a large stake (over your configured threshold)

### ❓ What if no recommendation is available?

If `ltdModelSuggestion = "N/A"`:

* Fall back to your default LTD based on feed/coverage
* Optionally use only the `ltdSuggestionEdl` value
* Ensure your system handles null values gracefully

### ❓ What are the API 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

### ❓ How does this integrate with other Insight Tech Services?

* Use player scoring APIs like Bot Score, Late Bet Score, sCCF, Marker Score
* Combine with event-level APIs like Event Profiling and Tournament Profiling
* The LTD API acts as the real-time decision layer based on those profiles

### ❓ Who should I contact for help?

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/live-time-delay-ltd-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.