Main lines and alternates, pre-game and live, from the sportsbooks we track for LIDOM, delivered via the Betstamp PRO odds screen or sportsbook API.
Market makers want an API to trade off. Pricing teams want JSON. Traders want a screen. Every Betstamp LIDOM feed ships in every form — same data, same refresh rate, same delivery SLA.
See LIDOM prices from the books we track, side-by-side in the Betstamp PRO Odds Screen, refreshed in real time.
The LIDOM odds API for trading desks, market makers, risk teams, and algo platforms. Pre-match and live LIDOM odds via REST pull or SSE stream — structured JSON across books in one schema.
/api/markets + SSE at /v1/marketsMain lines and alternates — pre-game and live, normalized into the same schema as every other league in your trading system.
LIDOM moneylines, pre-match and in-play.
LIDOM run lines and alternate run lines.
LIDOM game totals and team totals, over / under.
LIDOM first 3/5/7 innings and individual innings markets.
LIDOM first-inning run markets.
LIDOM game props in the same schema as the main lines.
Alternate LIDOM lines alongside the mains.
Tell us which books and markets you need and we'll build it out.
If you can hit a REST endpoint, you can pull LIDOM odds. Three steps, no scraping, no captcha headaches, no IP rotation.
Request a demo, scope your usage, and we issue a key scoped to LIDOM plus any other leagues and books you need. Trial keys available for evaluation.
A single GET on /api/markets returns LIDOM markets for the bet types and periods you specify. Filter by bet_types, is_live, include_alts, and book_ids — same shape as the docs.
Connect to /v1/markets via Server-Sent Events to receive LIDOM line moves as they happen — one JSON object per data: message. No polling, no client-side queue.
# Pull LIDOM run lines, full game # League codes for LIDOM are provided with your API key. curl -H "X-API-KEY: $BETSTAMP_API_KEY" \ "https://api.pro.betstamp.com/api/markets?league=<LEAGUE_CODE>&bet_types=spread&periods=FT" # Response (real schema, values illustrative, truncated) { "markets": [ { "id": "0192b4a1-8f13-7c2b-8629-aa3ef295e2f0", "odds": 2.05, "number": -1.5, "side": "Away", "side_type": "Away", "bet_type": "Spread", "period": "FT", "league": "<LEAGUE_CODE>", "is_alt": false, "is_live": false, "odd_provider_id": "{book_id}", "fixture_id": "01926d5e-819d-7b33-b7ff-bbe89e134958" } ] }
Pulling LIDOM odds book by book means a scraper per sportsbook, a schema per scraper, and a pipeline that breaks whenever one of them changes. Betstamp delivers all of them through one integration.
The /api/markets endpoint returns LIDOM odds from every book in your subscription in one response. Add or drop books with the book_ids parameter — no new integration.
Teams, players, bet types, periods, and alternate sets map to the same schema across books, so your model reads LIDOM the same way no matter which book priced it.
The Betstamp PRO Odds Screen lines up every LIDOM price by market, so the best available number and the hold are visible at a glance.
In-play LIDOM odds arrive in the same schema as pre-match, over the same endpoint and stream — no separate live integration.
Pull LIDOM into the PRO Odds Screen, the sportsbook API, or both — same pricing, same refresh rate, same normalized schema. Pick the delivery that fits your stack, switch later if it changes.
99.99% uptime SLA on the LIDOM feed. Slack channel with our trading desk. Schema changes upstream don't break your pipeline — we handle the maintenance.
A selection of the books with the deepest LIDOM coverage in our feed. More books price LIDOM than are shown here.
Other baseball leagues desks pull alongside LIDOM — or browse every league we cover.