> 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/integration/updates-and-synchronization.md). # Updates and synchronization ## Updates and synchronization Integrate TheSports API data through your backend. Store it locally before your application uses it. ### Integration requirements Integrate every TheSports API endpoint with a local database before using its data. Direct calls from frontend applications to TheSports API endpoints are not supported. ### Synchronization methods Most synchronization happens over HTTP: use the relevant API endpoint for the initial Full update and later Incremental updates. When working with **Real-time data** API endpoint, WebSocket is the recommended way to receive live changes. ### Update types * **Full update** retrieves the complete data set for the initial synchronization. * **Incremental update** retrieves new or changed records after the initial synchronization. Follow the sport-specific API endpoint documentation for its pagination, time parameter, and recommended request frequency. ### Request limit Each IP address can make up to 1,000 requests per minute. Requests beyond this limit are treated as invalid. ### Processing updates Save responses to the local database before applying local filters. Filtering before storage can discard required changes. Preserve update order when an API endpoint requires ordering. ### After a WebSocket reconnect For the **Real-time data** API endpoint, reconnect and resubscribe to the required topic after an interruption. Then use HTTP synchronization to check for data missed while disconnected. ### Next steps Review [WebSocket via MQTT](/integration/websocket-via-mqtt.md) for connection behavior. Check [Timestamps and ids](broken://spaces/dosu4ynmwSCtMBPWJpmP/pages/TbY3v7vP9McI0mJmAPNJ) before storing identifiers. --- # 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/integration/updates-and-synchronization.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.