For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Last updated

Was this helpful?