Bookmakers

An API that returns odds from many sportsbooks through one integration instead of one per book. SportsGameOdds covers 85+ books, and every one of them prices a given market under the same oddID, so comparing them is a lookup rather than a name-matching exercise. Adding a book to a request you already make is a parameter change, not new parsing code.

85+ in total, spanning traditional sportsbooks, betting exchanges and DFS platforms. Coverage varies by market rather than being uniform across all of them, so read byBookmaker on each odd rather than assuming every book prices every market.

Nine: FanDuel, DraftKings, BetMGM, Caesars, ESPN BET, Bovada, Unibet, PointsBet and William Hill. The free Amateur tier also limits the league list, the request rate and the refresh interval, so treat it as a way to build against real data rather than a way to run a product.

Pass bookmakerID to the events endpoint in lowercase, or a comma-separated list for several books at once. Build against the ID rather than the display name, since the two do not always match — William Hill is williamhill and ESPN BET is espnbet. Each book's price comes back under byBookmaker on every odd.

Yes. Alongside sportsbooks we carry exchanges such as Betfair Exchange and Novig, prediction markets including Kalshi and Polymarket, and DFS platforms like PrizePicks and Underdog. They arrive in the same schema under the same oddID as a sportsbook price, which is what makes comparing a DFS line against a book line a lookup rather than a mapping problem.

Not publicly. The major books do not offer developer APIs for their odds, which is why most products either scrape them or license an aggregated feed. SportsGameOdds provides them through one API in a single schema, so there are no unofficial endpoints to maintain and no per-book parsing to keep working.

Not a dedicated one. Leagues and sports each have a list endpoint; bookmakers do not. To find which books price a given market, query the markets endpoint, which returns the supported bookmakers per market by league. At runtime, read the keys of byBookmaker on each odd — that is the authoritative answer for that market at that moment.

Yes, though not for every market on every book. Each event carries event-level deeplinks under links.bookmakers, and individual odds carry bookmaker-specific deeplinks where available. Treat a missing deeplink as normal rather than an error, and check for one before rendering a link out to a book.

No. Billing is per event object rather than per market or per book, so one game counts once whether the response carries four books or eighty. Adding books to a request you were already making costs response size and nothing else.