{"id":3157,"date":"2026-08-03T10:00:00","date_gmt":"2026-08-03T10:00:00","guid":{"rendered":"https:\/\/oddspapi.io\/blog\/?p=3157"},"modified":"2026-07-18T17:38:52","modified_gmt":"2026-07-18T17:38:52","slug":"npb-odds-api","status":"publish","type":"post","link":"https:\/\/oddspapi.io\/blog\/npb-odds-api\/","title":{"rendered":"NPB Odds API: Live Japanese Baseball Odds in Python (Free Tier)"},"content":{"rendered":"

Nippon Professional Baseball is the strongest baseball league outside the United States, it runs from late March to October, and it fills the dead hours before the MLB slate starts. Most odds APIs either skip it or bury it under a generic baseball endpoint with two bookmakers attached. If you already scrape MLB prices, NPB is the obvious next league, and your existing code almost works on it.<\/p>\n

This guide pulls live NPB odds in Python: moneylines, run lines, totals and first-inning markets from 8 bookmakers including Pinnacle. It also covers the one thing that trips people up when they point MLB code at Japan, which is that the scoring environment is completely different and your thresholds will be wrong.<\/p>\n

NPB uses the same endpoints as MLB<\/h2>\n

Good news first. NPB sits under the same sport as MLB, sportId 13<\/code>, and uses the same market IDs. Winner is market 131<\/code>, the run line is the Handicap (incl. extra innings)<\/code> family, and totals are Over Under (incl. extra innings)<\/code>. Anything you built for the MLB odds API<\/a> ports across by changing one filter.<\/p>\n

import requests\n\nAPI_KEY = \"YOUR_API_KEY\"\nBASE_URL = \"https:\/\/api.oddspapi.io\/v4\"\n\ndef api_get(path, **params):\n    params[\"apiKey\"] = API_KEY          # query param, not a header\n    r = requests.get(f\"{BASE_URL}{path}\", params=params, timeout=30)\n    r.raise_for_status()\n    return r.json()\n\nfixtures = api_get(\"\/fixtures\", sportId=13,\n                   **{\"from\": \"2026-07-18\", \"to\": \"2026-07-27\"})\n\nnpb = [f for f in fixtures\n       if f.get(\"tournamentName\") == \"NPB\" and f.get(\"hasOdds\")]\n\nprint(len(npb), \"NPB fixtures with odds\")\nfor f in npb[:5]:\n    print(f[\"fixtureId\"], f[\"participant1Name\"], \"v\", f[\"participant2Name\"])\n<\/code><\/pre>\n
That returned 36 NPB fixtures with odds across a ten day window. Team names come back in English (Orix Buffaloes, Yomiuri Giants, Hokkaido Nippon-Ham Fighters), so you do not need to handle Japanese text to match fixtures.<\/p>\n
Pull the moneyline<\/h2>\n
The worked example is Orix Buffaloes against Hokkaido Nippon-Ham Fighters, fixture id1300103666777590<\/code>. Market 131<\/code> is Winner (incl. extra innings)<\/code>, with outcome 131<\/code> for the first participant and 132<\/code> for the second.<\/p>\n
FID = \"id1300103666777590\"\nbooks = api_get(\"\/odds\", fixtureId=FID)[\"bookmakerOdds\"]\n\ndef price(slug, market_id, outcome_id):\n    node = (books.get(slug, {}).get(\"markets\", {})\n                 .get(market_id, {}).get(\"outcomes\", {}).get(outcome_id, {}))\n    player = node.get(\"players\", {}).get(\"0\")\n    if not player or node.get(\"active\") is False:\n        return None\n    return player.get(\"price\")\n\nfor slug in sorted(books):\n    home, away = price(slug, \"131\", \"131\"), price(slug, \"131\", \"132\")\n    if home:\n        print(f\"{slug:20} {home:>7} {away:>7}\")\n<\/code><\/pre>\n
\n\n\n\n\n\n\n\n\n\n\n
Bookmaker<\/th>\nOrix<\/th>\nNippon-Ham<\/th>\n<\/tr>\n<\/thead>\n
pinnacle<\/td>\n2.10<\/td>\n1.806<\/td>\n<\/tr>\n
polymarket<\/td>\n2.128<\/td>\n1.852<\/td>\n<\/tr>\n
pointsbet.com.au<\/td>\n2.06<\/td>\n1.769<\/td>\n<\/tr>\n
draftkings<\/td>\n2.05<\/td>\n1.76<\/td>\n<\/tr>\n
caesars \/ williamhill<\/td>\n2.05<\/td>\n1.741<\/td>\n<\/tr>\n
kalshi<\/td>\n1.852<\/td>\n1.613<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
Eight bookmakers were on the fixture and 121 markets were on the board across them. Filter on active is False<\/code> rather than a truthy active<\/code> check, because the feed sometimes ships active: null<\/code> alongside a valid price.<\/p>\n
Two things to notice before you trust the board<\/h2>\n
First, caesars<\/code> and williamhill<\/code> quote 2.05 and 1.741 to the decimal, because they run the same pricing. Eight slugs collapse to six independent quotes here. Deduplicate before averaging or that one opinion gets double weight in your consensus number<\/a>.<\/p>\n
from collections import defaultdict\n\ngroups = defaultdict(list)\nfor slug in books:\n    quote = (price(slug, \"131\", \"131\"), price(slug, \"131\", \"132\"))\n    if None not in quote:\n        groups[quote].append(slug)\n\nprint(len(books), \"slugs ->\", len(groups), \"distinct quotes\")\nfor quote, slugs in groups.items():\n    if len(slugs) > 1:\n        print(\"  duplicate:\", quote, slugs)\n\n# 8 slugs -> 6 distinct quotes\n#   duplicate: (2.05, 1.741) ['caesars', 'williamhill']\n<\/code><\/pre>\n
Second, look at Kalshi. Its two prices imply 54.0% and 62.0%, which sums to 116%. That is not a competitive quote, it is a thin market on a league the exchange has little volume in. The two exchanges split hard here: Polymarket was the tightest book on the fixture at 100.99%, Kalshi the widest by a distance. Screen by implied total before you let any book into a consensus calculation.<\/p>\n
def book_percent(slug):\n    h, a = price(slug, \"131\", \"131\"), price(slug, \"131\", \"132\")\n    return (1\/h + 1\/a) if h and a else None\n\nfor slug in sorted(books):\n    bp = book_percent(slug)\n    if bp:\n        print(f\"{slug:20} {bp*100:6.2f}%\")\n\n# polymarket            100.99%\n# pinnacle              102.99%\n# draftkings            105.60%\n# pointsbet.com.au      105.07%\n# caesars               106.22%\n# williamhill           106.22%\n# kalshi                115.99%\n<\/code><\/pre>\n
De-vig the sharp price<\/h2>\n
Pinnacle carried a 2.99% margin on this game, which is tight for a non-US league.<\/p>\n
quote = {o: price(\"pinnacle\", \"131\", o) for o in (\"131\", \"132\")}\nimplied = {k: 1 \/ v for k, v in quote.items()}\ntotal = sum(implied.values())\n\nprint(f\"overround {(total - 1) * 100:.2f}%\")\nfor k, label in [(\"131\", \"Orix\"), (\"132\", \"Nippon-Ham\")]:\n    print(f\"{label:12} fair prob {implied[k]\/total:.4f}  fair odds {total\/implied[k]:.4f}\")\n\n# overround 2.99%\n# Orix         fair prob 0.4624  fair odds 2.1628\n# Nippon-Ham   fair prob 0.5376  fair odds 1.8600\n<\/code><\/pre>\n
Best available prices were 2.128 on Orix and 1.852 on Nippon-Ham, both at Polymarket, which beat Pinnacle on each side of the same game. Both still sit inside Pinnacle’s fair numbers of 2.1628 and 1.8600, so that is a line shopping result rather than a value claim. The three de-vig methods are compared in the no-vig odds guide<\/a>.<\/p>\n
NPB scores about two runs lower than MLB<\/h2>\n
This is the part that breaks ported MLB code. Japanese baseball plays in a lower scoring environment, and any total threshold tuned on MLB will be wrong. Rather than assert it, here are the main totals pulled from the same feed on the same days.<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n
NPB fixture<\/th>\nMain total<\/th>\nMLB fixture<\/th>\nMain total<\/th>\n<\/tr>\n<\/thead>\n
Orix Buffaloes<\/td>\n7.0<\/td>\nCleveland Guardians<\/td>\n7.5<\/td>\n<\/tr>\n
Yomiuri Giants<\/td>\n6.5<\/td>\nChicago Cubs<\/td>\n8.5<\/td>\n<\/tr>\n
Chiba Lotte Marines<\/td>\n7.5<\/td>\nToronto Blue Jays<\/td>\n9.5<\/td>\n<\/tr>\n
Yokohama DeNA BayStars<\/td>\n7.5<\/td>\nColorado Rockies<\/td>\n12.5<\/td>\n<\/tr>\n
Hiroshima Toyo Carp<\/td>\n6.0<\/td>\nPhiladelphia Phillies<\/td>\n8.5<\/td>\n<\/tr>\n
Tohoku Rakuten Golden Eagles<\/td>\n6.5<\/td>\nHouston Astros<\/td>\n9.0<\/td>\n<\/tr>\n
Median<\/strong><\/td>\n6.75<\/strong><\/td>\nMedian<\/strong><\/td>\n8.75<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
Two full runs of difference on the median. If your model flags anything under 7.5 as a low-total game, every NPB fixture triggers it. The Rockies at 12.5 show the other end of the range, which is Coors Field doing what Coors Field does.<\/p>\n
Totals resolve through the Over Under (incl. extra innings)<\/code> family. Each line is a separate market ID, so look them up instead of hardcoding.<\/p>\n
catalog = api_get(\"\/markets\", sportId=13)\ntotals = {m[\"marketId\"]: m.get(\"handicap\") for m in catalog\n          if m.get(\"marketName\") == \"Over Under (incl. extra innings)\"\n          and m.get(\"period\") == \"result\"}\n\nfor mid, market in books[\"pinnacle\"][\"markets\"].items():\n    if int(mid) in totals:\n        for oid, outcome in market[\"outcomes\"].items():\n            node = outcome.get(\"players\", {}).get(\"0\")\n            if node and outcome.get(\"mainLine\"):\n                print(\"main total\", totals[int(mid)], oid, node[\"price\"])\n\n# main total 7 ...\n<\/code><\/pre>\n
Read the mainLine<\/code> flag rather than guessing which rung of the ladder is the headline number. On this fixture Pinnacle’s 6.5 line priced at 1.813 over and 2.05 under, and the run line at 1.5 came in at 1.595 and 2.44.<\/p>\n
Settlement: NPB games can end in a tie<\/h2>\n
NPB regular season games are capped at 12 innings, so a game level at that point is recorded as a tie. MLB has no such rule, which means a two-way moneyline behaves differently across the two leagues.<\/p>\n
The feed labels the market Winner (incl. extra innings)<\/code> and ships it with two outcomes, no draw selection. How a tie settles is a bookmaker rules question rather than something the odds payload answers, and it varies by book. Check the settlement terms at whichever book you are pricing against before you grade positions automatically, and do not assume a stake is returned. This is the single most common way an MLB-shaped grading script produces wrong results on Japanese baseball.<\/p>\n
Free historical prices<\/h2>\n
hist = api_get(\"\/historical-odds\", fixtureId=FID,\n               bookmakers=\"pinnacle,bet365,draftkings\")   # max 3 per call\n\nsnaps = (hist[\"bookmakers\"][\"pinnacle\"][\"markets\"][\"131\"]\n             [\"outcomes\"][\"131\"][\"players\"][\"0\"])          # a LIST of snapshots\n\nprint(len(snaps), snaps[0][\"price\"], \"->\", snaps[-1][\"price\"])\n# 5 2.07 -> 2.1\n<\/code><\/pre>\n
Pinnacle recorded 5 price points on this fixture, drifting 2.07 to 2.10. NPB books post later and move less than MLB books, so the history is shorter. The historical response nests under bookmakers<\/code> rather than bookmakerOdds<\/code>, and players[\"0\"]<\/code> is a list instead of one price. Capture it into your own store and the sparse history stops being a problem, which the odds database guide<\/a> covers.<\/p>\n
What NPB coverage actually looks like<\/h2>\n
Being straight about the depth: NPB gets 8 bookmakers on a fixture where a marquee MLB game gets 17, and the run line and totals sit on 4 books rather than 10. Pinnacle, Polymarket and the US retail books carry it. First-inning markets are there but on two books.<\/p>\n
What you do get is a sharp reference price on every fixture, a full handicap and total ladder from Pinnacle, and 121 markets on a league most feeds ignore. For a league playing daily while MLB sleeps, that is enough to build on. Widen to the best price across the board with line shopping in Python<\/a>.<\/p>\n
Frequently asked questions<\/h2>\n
Is there an NPB odds API?<\/h3>\n
Yes. NPB fixtures sit under baseball, sportId 13, with tournamentName NPB. A ten day window returned 36 NPB fixtures with odds, priced by up to 8 bookmakers including Pinnacle, with 121 markets on a single game.<\/p>\n
Does NPB use the same market IDs as MLB?<\/h3>\n
Yes. Both sit under sportId 13, so Winner is market 131, run lines are the Handicap (incl. extra innings) family and totals are Over Under (incl. extra innings). MLB code ports over by changing the tournament filter.<\/p>\n
Why are NPB totals lower than MLB totals?<\/h3>\n
Japanese baseball plays in a lower scoring environment. Across six fixtures from each league on the same days, the median main total was 6.75 for NPB and 8.75 for MLB. Any threshold tuned on MLB totals needs retuning before it runs on NPB.<\/p>\n
How do NPB ties affect settlement?<\/h3>\n
NPB regular season games are capped at 12 innings and can end in a tie. The feed ships Winner (incl. extra innings) with two outcomes and no draw selection, so how a tie settles depends on the bookmaker’s rules rather than the odds payload. Check settlement terms before grading positions automatically.<\/p>\n
Can I get free historical NPB odds?<\/h3>\n
Yes, on the free tier, capped at three bookmakers per call. Pinnacle recorded 5 price points on the sample fixture. NPB books post later and move less than MLB books, so histories are shorter than you would see on a US game.<\/p>\n
Start pulling NPB prices<\/h2>\n
One free key covers 381 bookmakers across 69 sports, with sharp books and prediction markets in the same response and free price history. NPB is one filter away from code you have already written. Get your free API key<\/a> and point it at tonight’s Japanese slate.<\/p>\n