> 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/mapping-testing-and-go-live.md).

# Mapping, Testing & Go-Live

The final stretch: align your markets, make sure the system holds up under load, then switch to production.

## Step 4: Data Mapping

Align your internal catalog with LSports' structure before consuming the feed in production. Each entity below has a dedicated endpoint on the [Metadata API](/u/trade/integration/apis/metadata.md); work through them in order, since each level builds on the one before it.

| Entity           | Endpoint            | What you're mapping                                                                    |
| ---------------- | ------------------- | -------------------------------------------------------------------------------------- |
| **Sports**       | `/Sports/Get`       | Sport IDs to your internal sport tree                                                  |
| **Locations**    | `/Locations/Get`    | Countries and regions used for league grouping                                         |
| **Leagues**      | `/Leagues/Get`      | League IDs to your competitions                                                        |
| **Markets**      | `/Markets/Get`      | Market types to your bet-type catalog, the core of the mapping work                    |
| **Participants** | `/Participants/Get` | Teams and players (supports [pagination](/u/trade/integration/apis/api-pagination.md)) |
| **Fixtures**     | `/Fixtures/Get`     | Event-level metadata validation                                                        |

Review [Enumerations](/u/trade/enumerations.md) for status codes and field values, and [Message Structure](/u/trade/integration/message-structure/message-types-overview.md) for how these IDs appear in feed messages. For anything unclear in the market structure, contact your CSM.

Plan for this step: mapping typically takes 2–3 weeks and is the longest part of most integrations.

## Step 5: Stress Test

Once all integration work is complete, schedule a joint stress-test session with your Customer Enablement Manager (CEM) before going live. This is a 45-minute screenshare where LSports and your team review both sides' metrics together and run load and reconnection testing, to make sure everything built in [Reliability & Recovery](/u/trade/integration/reliability-and-recovery.md) works under real load before production.

Before scheduling, have your latency metrics available on a dashboard (Grafana or any graphing platform): the session compares your consumption and processing metrics against LSports' distribution metrics.

### What the session should validate

* Auto-reconnection and the full recovery sequence.
* Liveness detection and trading suspension: heartbeat freshness monitoring, and use of the Distribution Status API to verify feed state during disconnections.
* Snapshot and RMQ reconciliation behaving correctly under load.
* Behavior under high message rates (2,000 to 10,000+ msg/s). *Run by LSports.*
* Full-sport subscriptions, not just a narrow test slice.

## Step 6: Go Live

Once your system is ready and the stress test has passed, contact your CSM to schedule a go-live date. LSports will switch your account from testing to production and set up your ordered quota. *Done by LSports.*

{% hint style="success" %}
**You're integrated.** Keep the monitoring and recovery practices from [Reliability & Recovery](/u/trade/integration/reliability-and-recovery.md) running in production: they're what keeps the feed reliable day to day, not just at setup.
{% endhint %}

***

Next: [Quick Reference](/u/trade/integration/quick-reference.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 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.lsports.eu/u/trade/integration/mapping-testing-and-go-live.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.