> 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/live-data/introduction/system-communication/xml-messages-sent-from-the-client-system/login.md).

# Login

After connecting to the server, the client system needs to log in before it can start sending requests and receiving data.

**XML example**

```xml
<login>
<credential>
<loginname value="pavels"/>
<password value="..."/>
</credential>
</login>
```

**Login reply**\
In order to let the client system know whether the login attempt was successful, the server replies to login messages.

**XML example**

```xml
<login result="valid">
<user bookmakerid="1234"/>
</login>
```

***XML attributes definition***

<table><thead><tr><th width="144.5">Element</th><th width="176.0565185546875">Attributes</th><th>Description</th><th>Possible values</th></tr></thead><tbody><tr><td>login</td><td><em>result</em></td><td>Whether the login was successful or not</td><td>String, possible values:<br>valid = Login succesfull<br>invalid = Login failed</td></tr></tbody></table>

<br>


---

# 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/live-data/introduction/system-communication/xml-messages-sent-from-the-client-system/login.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.
