Main lines and alternates, pre-game and live, from the sportsbooks we track for NB I. A, 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 NB I. A feed ships in every form — same data, same refresh rate, same delivery SLA.
See NB I. A prices from the books we track, side-by-side in the Betstamp PRO Odds Screen, refreshed in real time and benchmarked against our True Line.
The NB I. A odds API for trading desks, market makers, risk teams, and algo platforms. Pre-match and live NB I. A 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.
NB I. A moneylines, pre-match and in-play.
NB I. A point spreads and alternate spreads.
NB I. A game totals and team totals, over / under.
NB I. A quarters and halves markets, each queryable on its own.
NB I. A game props in the same schema as the main lines.
Alternate NB I. A 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 NB I. A odds. Three steps, no scraping, no captcha headaches, no IP rotation.
Request a demo, scope your usage, and we issue a key scoped to NB I. A plus any other leagues and books you need. Trial keys available for evaluation.
A single GET on /api/markets returns NB I. A 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 NB I. A line moves as they happen — one JSON object per data: message. No polling, no client-side queue.
# Pull NB I. A spreads, full game # League codes for NB I. A 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": 1.91, "number": -3.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 NB I. A 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 NB I. A 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 NB I. A the same way no matter which book priced it.
The Betstamp PRO Odds Screen shows our True Line fair value side-by-side with every NB I. A price, so traders don't have to compute consensus from scratch. CLV-tested across 5+ seasons.
In-play NB I. A odds arrive in the same schema as pre-match, over the same endpoint and stream — no separate live integration.
Pull NB I. A 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 NB I. A 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 NB I. A coverage in our feed. More books price NB I. A than are shown here.
Other basketball leagues desks pull alongside NB I. A — or browse every league we cover.