Integration Guide

Your Integration Path

How you integrate with DEFEND depends on where your fixture and market data comes from.

Path	Your setup	What you send to DEFEND
TRADE-exclusive	LSports TRADE is your sole data source and you do not apply additional margin to TRADE odds outside of TRADE	Bet slips only — LSports handles fixture and market metadata automatically
External data sources	You use additional providers, a non-TRADE data source, or apply your own margin to TRADE odds outside of TRADE	Fixture metadata, markets data, and bet slips

Using TRADE exclusively? You do not need to send fixture or market metadata. LSports consumes and processes that data on your behalf. Skip ahead to Betslips and follow the bet slip integration steps only.

Note: This applies only if you consume TRADE odds without modifying them outside of TRADE. Margin configured within TRADE is fine — but if you apply your own margin to the odds on your side, send fixture and market metadata as described below.

If you are unsure which path applies to your setup, contact your CSM.

If you use external data sources or additional providers alongside TRADE, continue with the full guide below.

DEFEND integration process overview

To enable our Risk Management System to monitor and manage your trading activity effectively, integration with LSports Defend requires only two simple data connections:

Fixtures and Markets Data

Provide your InPlay and PreMatch fixtures and markets feed. This allows our system to analyze real-time betting opportunities and assess risk dynamically.

Betslips

Send all betslip information associated with your users. You can use any unique user identifier (no personal or sensitive data is required).

Data Transmission

All data is transferred via a secure HTTP channel using authentication tokens for validation. Integration is performed through our HTTP API endpoints.

Next Steps

The following pages will guide you through:

The data models for Fixtures, Markets, and Betslips.

The API endpoints and required authentication flow.

Example payloads and validation requirements for a seamless integration.