> 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.md). # Integration Connect to the TRADE data stream Everything you need to get your integration running on RabbitMQ, from your first credentials to a stable, production-ready feed. Work through the sections in order, or jump straight to the one you need. ## Sections * [**Getting Started**](/u/trade/integration/getting-started-steps.md) (Steps 1–2): Receive your credentials from LSports and enable distribution on your package. * [**Connection Setup**](/u/trade/integration/connection-setup.md) (Step 3, Part A): Connect to RabbitMQ and configure how you consume messages. * [**Reliability & Recovery**](/u/trade/integration/reliability-and-recovery.md) (Step 3, Part B): Heartbeats, recovery sequencing, and the practices that keep your feed stable. * [**Mapping, Testing & Go-Live**](/u/trade/integration/mapping-testing-and-go-live.md) (Steps 4–6): Align your markets, stress test, and switch to production. * [**Quick Reference**](/u/trade/integration/quick-reference.md): A condensed, single-page summary of the whole integration. ### Typical timeframes | Phase | Typical timeframe | | ------------------------------------------- | -------------------------------------------------------------------------- | | **Getting Started** (Steps 1–2) | Same day as your kick-off call with the enablement team | | **Connection Setup** (Step 3, Part A) | Up to 3 days using an SDK; longer for custom RabbitMQ implementations | | **Reliability & Recovery** (Step 3, Part B) | About 1 week | | **Data Mapping** (Step 4) | 2–3 weeks, the longest part of most integrations | | **Stress Test & Go-Live** (Steps 5–6) | A 45-minute joint session, scheduled once all integration work is complete | Timeframes are typical for a dedicated engineering team and vary by stack and scope. ### How this guide is organized The path from credentials to go-live is short on paper, six steps, but two of them (connecting to RabbitMQ, and keeping that connection healthy) are where most of the engineering work actually lives. This guide gives that work its own two sections rather than folding it into a single dense step, so it's easier to come back to later when you're tuning monitoring or debugging a reconnect. *** ## Integration Resources ### Connection & Messaging * [RabbitMQ Connection Setup](/u/trade/integration/rmq-connection/connection-and-consumption-setup.md) * [Message Deserializing](/u/trade/integration/rmq-connection/message-deserializing.md) * [Market/Bet Message Handling](/u/trade/integration/rmq-connection/market-bet-message-handling.md) * [How to Work with TRADE Feed](/u/trade/integration/rmq-connection/how-to-work-with-trade-feed.md) ### Message Structure * [Message Types Overview](/u/trade/integration/message-structure/message-types-overview.md) * [Fixture Messages](/u/trade/integration/message-structure/fixture.md) * [Market Messages](/u/trade/integration/message-structure/market.md) * [Livescore Messages](/u/trade/integration/message-structure/livescore.md) * [Settlement Messages](/u/trade/integration/message-structure/settlement.md) ### APIs * [Metadata API](/u/trade/integration/apis/metadata.md) * [Subscription API](/u/trade/integration/apis/subscription.md) * [Distribution API](/u/trade/integration/apis/distribution.md) * [ComboBuilder API](/u/trade/combo-builder.md) * [Snapshot API](/u/trade/integration/apis/snapshot.md) ### SDKs * [SDK Overview](/u/trade/integration/sdk/sdk-overview.md) * [.NET SDK](/u/trade/integration/sdk/sdk-installation-guide-.net.md) * [Java SDK](/u/trade/integration/sdk/sdk-installation-guide-java.md) * [Node.js SDK](/u/trade/integration/sdk/sdk-installation-guide-nodejs.md) ### Code Samples * [PHP](/u/trade/integration/code-samples/rmq-consumer-php.md) * [Go](/u/trade/integration/code-samples/rmq-consumer-go.md) * [Python](/u/trade/integration/code-samples/rmq-consumer-python.md) * [Node.js](/u/trade/integration/code-samples/rmq-consumer-node.js.md) * [C#](/u/trade/integration/code-samples/rmq-consumer-c.md) --- # 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.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.