PulseScore API Review 2026

PulseScore is a sports odds API that aggregates live and pre-match data from 30+ bookmakers, including Bet365, Pinnacle, DraftKings, FanDuel, and Betfair. It delivers odds through both REST endpoints and a WebSocket feed that broadcasts updates roughly every second.

The focus is on speed and normalization. Each bookmaker gets its own base URL path, but the response schema stays the same across all of them. You write one parser and reuse it whether you are pulling from Bet365 or Pinnacle. The product is relatively new and lean: 14+ sports, a normalized market schema, and a straightforward pricing ladder from free to EUR 249/mo.

PulseScore lists 14+ sports: soccer, tennis, basketball, ice hockey, baseball, American football, cricket, rugby (league and union), volleyball, handball, table tennis, esports, horse racing, and greyhounds. Soccer and tennis get the most emphasis in the documentation and examples.

Bookmaker coverage sits at 30+ and growing, with new books added roughly weekly according to the site. The set includes major international operators (Bet365, Pinnacle, Paddy Power, Betfred, Bwin, Unibet AU) and US books (FanDuel, DraftKings, BetOnline). That puts it in a middle tier: broader than single-source Pinnacle feeds, narrower than the large aggregators that list hundreds of books.

Market types use a canonical naming scheme. match_winner and total_goals are documented, with a rawName fallback for markets the normalization layer has not mapped yet. The documentation does not list a full set of canonical market types, so you should check which markets are live for your target sport before you commit. There is no mention of player props, futures, or closing lines in the docs.

Odds are returned in decimal format. If your application needs American odds, you will convert on your side.

The WebSocket feed is the core of PulseScore's pitch. You connect to a bookmaker-specific URL (wss://api.pulsescore.net/api/{bookmaker}/ws/live), pass your API key as a query parameter, and receive broadcast frames roughly every second with all live events for your selected sport. That cadence is fast enough for live odds displays and in-play alerting.

REST endpoints cover both live and pre-match data. Live events come from /live-events; pre-match data is organized by sport and league (/{sport}/leagues, /{sport}/events). Authentication uses an X-Secret header on all requests.

The architecture separates bookmakers at the URL level. Each book has its own path prefix, so a request to /api/v3/bet365/live-events returns Bet365 data only. If you want to compare across books, you make one request per bookmaker. That is a different model from aggregators that return all books in a single response, and it means your request count scales with the number of books you track. Plan your rate limits accordingly.

Pricing is published in euros:

• Basic (free): 500 requests per month, 1 request/second per bookmaker, no WebSocket. No card required.
• Starter, EUR 20/mo: 30,000 requests/month, 1 request/minute per bookmaker, no WebSocket.
• Pro, EUR 79/mo: unlimited requests, 1 request/second, 1 WebSocket connection (single sport).
• Max, EUR 149/mo: unlimited requests, 3 requests/second, 3 WebSocket connections (multi-sport).
• Ultra, EUR 249/mo: unlimited requests, 5 requests/second, 5 WebSocket connections.

The free tier is minimal. Five hundred requests per month works out to roughly 16 per day, which is enough to test the response shape but not enough to run a live application. WebSocket access, the main draw, starts at the Pro tier (EUR 79/mo).

Note the Starter tier rate limit: 1 request per minute per bookmaker. That is much slower than the other tiers and makes Starter impractical for anything that needs fresh data. If you need real utility beyond the free trial, the jump to Pro is steep.

PulseScore focuses on live and pre-match odds delivery. Several features that other odds APIs include are absent here:

• No closing lines or historical odds archive. The site mentions a 30-day results feed from select bookmakers, but there is no endpoint for closing prices or historical line movement. If your workflow depends on historical odds for backtesting or CLV analysis, you will need a second provider.
• No player props. The documented market types are game-level (match winner, totals). Props are not mentioned.
• No stats or scores. PulseScore delivers odds only. You will pair it with a stats source if you need box scores, standings, or schedules.
• No MCP server. There is no Claude or AI-assistant integration.
• No bet settlement or results. You get prices, not outcomes.

These gaps are not unusual for a newer, focused product. But they mean PulseScore is an odds pipe, not an all-in-one data platform. Plan your stack accordingly.

PulseScore fits a specific use case: live odds display and cross-book comparison on game-level markets. If you are building an odds-comparison site or a live alerting tool and you need per-second updates from Bet365, Pinnacle, and a handful of other major books, the WebSocket feed delivers that at a reasonable price.

It also suits developers who want international coverage beyond the US-only providers. Horse racing, greyhounds, cricket, and rugby are not common in the US-focused odds API market, and PulseScore covers them.

Skip it if your work depends on player props, closing lines, or historical data. Skip it too if you need hundreds of bookmakers in a single request rather than querying each book separately. For broader coverage or analytical features, compare options in the live sports odds API directory.

PulseScore is a clean, fast odds pipe. The per-second WebSocket feed and normalized schema across 30+ bookmakers solve the core problem of getting live prices into your application without scraping. The per-bookmaker URL model is unusual and adds request overhead if you track many books, but it keeps each response lean.

The gaps are straightforward: no props, no history, no stats, no settlement. If those matter to your use case, PulseScore is not the right primary provider. If you need a focused live odds feed with Bet365 and Pinnacle included, and the feature set above covers your requirements, the free tier costs nothing to test.