> 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/betlink-integration/backend-integration/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
