LSports API Review 2026

LSports is an enterprise sports data platform headquartered in Israel that has been operational since 2012. The company provides odds feeds, live scores, fixtures, statistics, and settlement data to sportsbook operators and betting platforms. It positions itself as a full-stack data layer: you buy one vendor and get pre-match odds, in-play odds, scores, results, and market settlements in a single integration.

The scale numbers are large. LSports claims 100+ sports, 15,000+ leagues, 2,500+ markets, and 175,000+ pre-match fixtures per month alongside 100,000+ in-play events. Those figures put it firmly in the enterprise tier alongside Sportradar and Betradar, not in the developer-API segment where you grab a key and start pulling JSON. If you want that kind of quick start, browse the full sports odds API directory instead.

The coverage spans traditional sports and extends into markets that smaller providers skip:

• Traditional sports: football (Premier League, La Liga, Bundesliga, Serie A, Champions League), basketball (NBA, NCAA basketball), American football (NFL, NCAA football), baseball (MLB), ice hockey (NHL), tennis, volleyball, handball, cricket, and horse racing.
• Markets: 2,500+ market types across pre-match and in-play, which suggests deep prop and derivative coverage, not the moneyline/spread/total basics.
• Data beyond odds: live scores, fixtures, standings, player statistics, team statistics, full-time results, and settlement data.
• Historical data: available for both pre-match and in-play events, which matters for backtesting and model training.

The site does not publish a bookmaker count. That is a gap. Enterprise platforms often aggregate from dozens of sources, but without a number it is hard to know whether you are getting 20 bookmakers or 200. Ask during the sales process.

LSports claims "close to zero" latency, which it quantifies elsewhere as 0 to 1 seconds. For a pre-match odds feed that is fast. For live in-play data where you are reacting to score changes mid-game, one second can matter depending on the use case.

The public docs site carries the full TRADE integration guide, an OpenAPI file and official SDKs for .NET, Java and Node.js (checked November 2026). The TRADE integration docs describe a RabbitMQ (AMQP) push stream rather than a WebSocket. The directory counts any push feed as streaming, so it marks that column yes. The technical details are on the docs site; pricing and package scope come from the sales conversation.

LSports supports 25 languages for its data, which signals a global client base. The 24/7 customer support and the claim that 70% of the team works in R&D round out the enterprise pitch.

Pricing is not published. The directory places LSports at the five-dollar-sign tier, the highest in our system, which makes it one of the most expensive options listed. There is no free tier. A trial exists, but only through sales contact, not through a self-serve signup page.

This is the standard enterprise data model: custom quotes, annual contracts, and packaging that depends on which sports, markets, and data types you select. If you are comparing costs against developer-friendly APIs that charge $50 to $300 a month, LSports is a different category. The per-month number will likely have four or five digits.

That pricing reflects the scope. You are paying for 100+ sports, settlements, statistics, and a dedicated support team, not for a single odds endpoint. Whether that scope matches your needs is the question worth answering before you start the sales process.

LSports doesn't hand out self-serve keys. The "Free Trial" button on its site opens a demo request form, and access starts there, with a demo and a kickoff call. Your Customer Success Manager then sends three credentials in an activation email: a Username (an email address), a Password and a numeric Package ID (checked November 2026).

Those three values work as the key. TRADE's REST calls send them in the JSON body as PackageId, UserName and Password rather than in a header, and the same username and password open the RabbitMQ feed. The API Tokens screen in the platform, which issues a Client ID and Secret Key, serves ComboBuilder rather than the odds feed.

The trial is a guided TRADE evaluation of about 14 days on production data. Nothing in the evaluation guide asks for a card, and in-play fixtures are quota-limited while it runs.

The sample calls POST https://stm-api.lsports.eu/Sports/Get, the metadata endpoint that lists sports. There's no single API key, so it reads three environment variables and sends them in the JSON body. Every response comes in the same envelope: a Header with HttpStatusCode and an Errors list when a call fails, and a Body whose Sports list holds objects with Id and Name. Paths and fields are from the docs, checked November 2026, with the field casing taken from LSports' official Node.js SDK.

import os
import requests

payload = {
    "PackageId": int(os.environ["LSPORTS_PACKAGE_ID"]),
    "UserName": os.environ["LSPORTS_USERNAME"],
    "Password": os.environ["LSPORTS_PASSWORD"],
}
resp = requests.post("https://stm-api.lsports.eu/Sports/Get", json=payload, timeout=30)
data = resp.json()

header = data["Header"]
if header.get("Errors"):
    raise SystemExit(f'{header["HttpStatusCode"]}: {header["Errors"][0]["Message"]}')

for sport in data["Body"]["Sports"][:10]:
    print(sport["Id"], sport["Name"])

For odds, TRADE pushes updates over RabbitMQ, and the docs include a Python consumer built on pika for that queue. The REST Snapshot API at stm-snapshot.lsports.eu fills gaps after a disconnect.

The docs set general defaults for every TRADE REST API. The integration guide allows 5 concurrent requests, the same request once every 5 seconds and about 1 call per second per endpoint. Snapshot calls get their own rule: a filtered request once per second, an unfiltered one every 15 seconds, and nothing for fixtures that ended more than 24 hours earlier (checked November 2026). On the push side, a queue that reaches 10,000 unconsumed messages shuts down. The docs show no 429 format; errors arrive in the response Header.

The LSports docs are public: the full TRADE integration guide, an OpenAPI file for the customer API, and RabbitMQ consumer samples in six languages, Python included. Official SDKs cover .NET and Java on GitHub and Node.js on npm, all under the trade360 name. Uptime sits on the status page, planned changes on the docs' Upcoming Changes page, and release notes at feedback.lsports.eu. An MCP connection, ARENA360 AI Access, is in beta for selected operators. Support runs 24/7 by live chat, plus tickets at support.lsports.eu and a dedicated Slack channel during an evaluation.

LSports targets a specific buyer profile:

• Sportsbook operators building or running a betting platform who need odds, scores, settlements, and statistics from a single vendor.
• Trading teams at established betting companies who need deep market coverage (2,500+ types) and low-latency delivery to power risk management.
• Data-heavy platforms that need player and team statistics alongside odds, saving the cost of integrating a separate stats provider.

Skip it if you are a developer building an odds comparison tool, a model that needs one or two sports, or anything where a $50/month API covers the data you actually use. LSports solves the "I need everything from one vendor" problem. If you do not have that problem, you are overpaying. For lighter-weight alternatives that let you start today, check the free odds API options.

The enterprise sports data market has a few dominant players. Sportradar is the largest and most visible. Betradar (Sportradar's B2B arm) powers a large share of European sportsbooks. LSports positions itself as the independent alternative to that duopoly, with comparable coverage numbers and a pitch built on customization and support responsiveness.

Compared to developer-focused APIs, the trade-offs are clear. LSports gives you more data types, more markets, and a dedicated support team. In return, you give up self-serve access, transparent pricing, and the ability to evaluate the product in an afternoon. That trade-off is fine if you are an operator with a procurement budget. It is a poor fit if you want to prototype first and scale later.

Public documentation is no longer a gap. The docs site is open, so you can read the API reference and the SDK code before you talk to sales, and judge the technical fit on your own.

LSports is a full-stack enterprise data platform that bundles odds, scores, statistics, and settlements into one vendor relationship. The coverage numbers (100+ sports, 2,500+ markets, 15,000+ leagues) are genuine enterprise scale, and the 2012 founding date gives it a long operating track record.

The friction is also genuine. No public pricing, no self-serve trial and no free tier, though the documentation is public. You are buying into a sales-driven procurement process. If your organization already buys data this way, LSports belongs on the shortlist alongside Sportradar. If you want to start building today with a credit card, pair a self-serve aggregator from the directory with an LSports evaluation once the product is proven.

Last updated: 2 November 2026 · How providers get listed