> 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/thesports-docs/faq.md).

# FAQ

#### **What's the relationship between competition, season, and stage?**

A competition can have multiple seasons. Each season can contain multiple stages. A stage may be divided into groups. Each group can contain multiple rounds of matches.

For example, the World Cup is a competition.

It has different seasons, such as 2014, 2018, and 2022. The 2022 season included several stages, such as the Group Stage, Semi-finals, and Final.

The Group Stage was divided into multiple groups, such as Group A, Group B, and Group C. Each group included three rounds of matches.

***

#### **How does the match status change during overtime and a penalty shootout?**

If a match proceeds to overtime or a penalty shootout, the match status changes as follows:

```
Second half -> End -> Overtime -> End -> Penalty shootout -> End
```

The corresponding status values are:

```
4 -> 8 -> 5 -> 8 -> 7 -> 8
```

Match Status `8` (End) may indicate the end of the second half, overtime, or the entire match. It does not always mean that the match has finally ended.

***

#### **How to determine whether the match has finally ended？**

There is no field that directly indicates whether match status `8` is final.&#x20;

When the match status changes to `8` (End), continue monitoring it for 10 minutes. If the status does not change during this period, you can treat the match as finally ended.

***

#### **How is the final score calculated?**

1\. If `Overtime score` is not `0-0`:&#x20;

```
Final score = Overtime score + Penalty shootout score
```

2\. If `Overtime score` is `0-0`:

```
Final score = Score (regular time) + Penalty shootout score
```

***

#### **How to synchronize the deleted data?**

TheSports performs daily data quality checks and deletes any incorrect or duplicate records as soon as they are identified.&#x20;

The [`Delete`](/thesports-docs/basic-data/delete.md) API endpoint under Basic Data allows customers to retrieve the ids of records deleted within the previous 24 hours and remove the corresponding records from their local databases.&#x20;

Integrating this endpoint is required to prevent deleted records from remaining in local data and to keep the data consistent with the latest data from TheSports.&#x20;

We recommend calling this endpoint once every 1 to 5 minutes.

***

#### **How to determine whether lineup data is available for a match？**

You can use either of the following methods:

1. Check the `lineup` field returned by one of the match schedule API endpoints：

   * [**Match(recent)**](/thesports-docs/basic-data/match-recent.md)
   * [**Schedule and Results - date query**](/thesports-docs/basic-data/schedule-and-results-date-query.md)
   * [**Schedule and Results - season query(newest season)**](/thesports-docs/basic-data/schedule-and-results-season-query-newest-season.md)
   * [**Match**](/thesports-docs/database-data/match.md)
   * [**Schedule and Results - season query(all season)**](/thesports-docs/database-data/schedule-and-results-season-query-all-season.md)

   If its value is `1-yes`, you can synchronize the [**Single match lineup**](/thesports-docs/basic-data/single-match-lineup.md) API endpoint. every 1 to 3 minutes.
2. Use the [**Data update**](/thesports-docs/basic-info/data-update.md) API endpoint. It returns data changed within the past 120 seconds. When lineup data for a match is updated, the `match_id` field includes the corresponding match id. Use this match id to retrieve the latest lineup data from the **Single match lineup** API endpoint.

We recommend using the second method.

***

#### **How to retrieve updated lineup data for historical matches over 30 days？**

The [**Data update**](/thesports-docs/basic-info/data-update.md) API endpoint returns data changed within the past 120 seconds. If the lineup for a historical match is updated, the API endpoint returns that match even if it took place more than 30 days ago.

After receiving a `match id` from the **Data update** API endpoint, use it to request the [**Single match lineup**](/thesports-docs/basic-data/single-match-lineup.md) API endpoint within 120 seconds. After this period, the API endpoint will no longer return the updated lineup data for that historical match.

For example, consider the Norwich City vs. Watford match in the EFL Championship:

```
Match time: 2024-09-21 19:30
Match id: 4jwq2ghez8d0m0v
Data update time: 2026-08-21 15:00
```

If the **Data update** API endpoint returns this `match id` at `15:00`, use it to request the **Single match lineup** API endpoint before `15:02`.

A request made at `15:03` will return no lineup data for this match.

***

#### **What do positive and negative Asian handicap values mean?**

* A positive value indicates a handicap for the home team.
* A negative value indicates a handicap for the away team.

***


---

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