> 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/help-center/football/suggestions-for-the-score-push-mechanism.md).
# Suggestions for the score push mechanism
We do not recommend using the `incidents` data from the [**Real-time data**](/thesports-docs/basic-data/real-time-data.md) API endpoint to trigger frontend notifications.
The `incidents` data is fully updated in each response.
For example, when a goal is scored, the API endpoint returns a `goal` incident. If the goal is later cancelled because of an earlier foul, the `goal` incident is omitted from the next response. As a result, you cannot detect the cancelled goal by comparing incident data or notify users of the cancellation.
We recommend using the `score` field from the **Real-time data** API endpoint to trigger score updates.
For example, if the previous score was `1-0` and the goal is later cancelled, the next response will report `0-0`. Compare consecutive `score` values to determine whether a goal was scored or cancelled.
**Note:** The `incidents` data in the **Real-time data** API endpoint is fully updated in each response. After retrieving a response, overwrite the previously stored incident data.
If you need to process incident data incrementally, add an `order` sequence to each incident and create a composite unique key using the Match id and the order, for example:
```
match_id + order
```
For each subsequent request, use this key to determine whether an incident is new before storing it.
The `incidents` data is intended for direct display only and should not be used to trigger frontend notifications. See the screenshot below for an example.
---
# 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/help-center/football/suggestions-for-the-score-push-mechanism.md?ask=&goal=
```
`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.