Mapping, Testing & Go-Live

Align your markets, stress test, and switch to production

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; 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)
Fixtures	/Fixtures/Get	Event-level metadata validation

Review Enumerations for status codes and field values, and Message Structure 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 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 CEM has cleared you for production, 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.

You're integrated. Keep the monitoring and recovery practices from Reliability & Recovery running in production: they're what keeps the feed reliable day to day, not just at setup.

---

Next: Quick Reference