> 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/betlink-integration/bet-placement.md).

# Bet Placement

The betslip is built directly in the BetLink UI and betslips are submitted to the BetLink back end. BetLink performs the crucial step of validating the price for the selection being placed and then propagates the bets to the operator API. The operator is responsible for evaluating the validity of the bet placement for any given user. This includes checks on available funds, blocked betting for regulatory reasons, stake caps, personal cool offs etc. BetLink is responsible for assessing the price and liveness of the selection.

For more information about bet placement flow consider reading [operator authentication flow.](/betlink-integration/front-end-integration/operator-authentication.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/betlink-integration/bet-placement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.