> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/integration/quick-reference.md). # Quick Reference A condensed, single-page summary of the whole integration A condensed, single-page summary of the whole integration. Use it to orient yourself or hand to a teammate. ### Steps 1–2: Credentials & distribution * Username / Password / Package ID provided by LSports. * `/Distribution/Start` and `/Distribution/Stop` control your feed. * Poll Distribution Status every \~5 seconds; target 0 messages in queue, investigate at 500 or more, recover at 10,000. ### Step 3: Connection, reliability & recovery * Prefetch \~100, no-ack/auto-ack; separate consumption from processing; route by message type and headers. * Recovery order: Start distribution, connect and cache, snapshot (in parallel), reconcile, resume. * Heartbeat every 5 seconds; no heartbeat for more than 12 seconds triggers recovery. Distribution active status `false` also triggers the recovery sequence. * Sequence gaps of 1–2 are normal; watch trends, not isolated gaps. * Snapshot is for recovery/enrichment only, filtered by last heartbeat; available up to 24 hours post-fixture. * Rate limits: 5 or fewer concurrent requests, 1 or fewer per second per endpoint. ### Steps 4–6: Mapping, testing & go-live * Metadata API endpoints (Sports, Locations, Leagues, Markets, Participants, Fixtures) for catalog alignment, in that order. * Joint stress test validates recovery, liveness detection and trading suspension, reconciliation, and high-volume behavior. * CEM clears you for production; CSM then schedules go-live, and LSports switches the account to production and configures quota. Questions? Reach out to your CSM or CEM at any step. --- # 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.lsports.eu/u/trade/integration/quick-reference.md?ask=&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.