> 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/backend-integration/introduction.md).

# Introduction

The BetLink backend controls the BetLink experience. Bets are placed, resulted and also, if necessary, voided by the BetLink backend. The BetLink backend does this by sending RESTful requests to the operator's wallet.

Before the bet placement route can occur, the authorisation pathway must be completed. This can be viewed as a login/handshake proving that the user is indeed genuine and logged into the operator's platform before any bet placement activity can take place. Voiding and resulting can take place without authorisation because they can theoretically occur a long time after bet placement.

The backend integration with the BetLink platform requires the operator to expose a RESTful API to IMGA according to IMGA's technical documentation herein.

BetLink requires 5 simple endpoints to be exposed, as detailed in the 'endpoint' sections below.

We expect the operator to generate and provide us with an API key per environment that controls access to the defined wallet API.


---

# 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/backend-integration/introduction.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.