> For the complete documentation index, see [llms.txt](https://docs.thesports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thesports.com/overview.md).

# Overview

Shared onboarding and integration guidance for TheSports products.

## TheSports API Documentation

Integrate historical and real-time sports data across TheSports products.

Most data synchronization uses HTTP, including the initial Full update and later Incremental updates. For the **Real-time data** API endpoint, MQTT over WebSocket is recommended for receiving live changes.

{% columns %}
{% column %}

#### [Make your first request](/get-started/quickstart.md)

Authenticate and call a documented API endpoint.
{% endcolumn %}

{% column %}

#### [Receive live updates](/integration/websocket-via-mqtt.md)

Connect with MQTT over a TLS WebSocket.
{% endcolumn %}

{% column %}

#### [Choose a sport](#choose-a-sport)

Find the endpoint reference for your sport.
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
**Shared hosts:** 

HTTP API `api.thesports.com`; 

MQTT over WebSocket `mq.thesports.com:443` with TLS.
{% endhint %}

### Choose a sport

| Sport         | Sport        | Sport      |
| ------------- | ------------ | ---------- |
| Football      | Basketball   | Tennis     |
| LOL           | DOTA2        | CSGO       |
| Volleyball    | Baseball     | Cricket    |
| Ice Hockey    | Handball     | Water Polo |
| Badminton     | Table Tennis | Snooker    |
| A.M. Football | F1           |            |

Each sport space contains its API endpoint and schema reference.

### Start here

1. Obtain credentials and whitelist access.
2. Choose a sport and API endpoint.
3. Make the initial HTTP request.
4. Connect to real-time updates when needed.

### Documentation map

* **Documentation** provides shared integration guidance.
* **Sport spaces** provide API endpoint and schema reference.
* **Help Center** provides operational explanations and support articles.


---

# 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.thesports.com/overview.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.