Skip to content
sportdex.

Betting exchange · United Kingdom

Matchbook Exchange

UK betting exchange offering a REST API for markets, offers and account data; read-only market data reportedly works without login, trading needs a funded account.

Facts verified against the provider's site on

Commercial use: not disclosedBetting use: not disclosedToo little discussion
30

SportDex Score

#139 of 233 sports APIs

See the full ranking →
33

Brand demand, developer discussions, GitHub repos and videos

—

Tone of public discussions, liked vs criticised points, reliability complaints; not enough public discussion to judge.

15

Public prices, docs, terms and coverage you can check before calling sales

38

Free access, docs, SDKs, OpenAPI, sandbox, realtime delivery, ecosystem

Computed from public data only; uptime and latency are not measured yet. Enterprise feeds that sell by contract score lower on transparency by design. How the score works

Starting price
Not public
Free access
Not disclosed
Sports
1 (Multi-sport (40+))
Live data
Not disclosed
Delivery
Polling only (REST)
Discussions
0 threads
GitHub adoption
17 repos

Best for

Not enough public detail to say.

Reading betting exchange marketsAutomated trading on an exchange

Not ideal for

Nothing stated on its pages.

Limitations to check

  • − Trading requires a funded exchange account
  • − No pricing or terms pages were available to check access rules

Written from the provider's own pages (source).

Last checked 2026-11-03

Matchbook Exchange at a glance

How much does Matchbook Exchange cost?
Matchbook Exchange does not publish prices on the pages we checked.
Does Matchbook Exchange have a free tier?
Matchbook Exchange does not say whether a free tier exists. Check https://www.matchbook.com.
What does Matchbook Exchange cover?
Matchbook Exchange is a betting exchange. Its sports: Multi-sport (40+); data: Trading & risk, Odds.
Does Matchbook Exchange have a WebSocket or streaming API?
No streaming is listed. Matchbook Exchange delivers data by REST, so you poll for updates.
What do developers say about Matchbook Exchange?
UK betting exchange with a REST API. No forum discussion, only GitHub: community wrappers in R and JavaScript, an MCP server for placing bets, and a few trading projects. A video describes the exchange as having lower commission than Betfair, interesting for US sports. No real feedback on API quality, limits or docs.
What are the alternatives to Matchbook Exchange?
Close alternatives in the SportDex catalog: Polymarket, Smarkets, BETDAQ, SX Bet, Betfair Exchange API.

Commercial decision

Pricing & plan limits

No public price list. Check the provider site.

Site blocked crawler; based on search snippets and third-party SDK pages. Exchange commission only, no plans published. Docs URL unconfirmed (from a third-party blog); auth type (session token) approximated as bearer. Country inferred.

Before choosing a paid plan, confirm

• What counts as one request (per call, per market, per region?)

• What happens when you exceed the quota: blocked or billed

• Whether live and historical data are on your plan

• Whether your use (public app, betting, resale) is licensed

The critical question

Data coverage

Sports
Multi-sport (40+)
Data types
Trading & riskOdds
Key competitions
Not disclosed
Competitions
Not disclosed
Live / in-play
Not disclosed
Women's competitions
Not disclosed
Betting markets
Not disclosed
Bookmaker regions
Not disclosed
Bookmakers
Not disclosed
History depth
Not disclosed
Update frequency
Not disclosed
Name languages
Not disclosed
ID mapping
Not disclosed

Coverage often depends on the plan; confirm the exact league and season on your plan.

Before you build

Usage rights & access

Commercial use
Not disclosed
Betting products
Not disclosed
Redistribution
Not disclosed
Storing data
Not disclosed
Attribution
Not disclosed
Logos & photos
Not disclosed
Who can buy
Not disclosed
Verification (KYC)
Not disclosed
Not available in
Not disclosed
Only available in
Not disclosed

Developer-ready evaluation

Integration & documentation

Protocols
REST
Formats
JSON
Authentication
bearer
SDKs
python, go, r
OpenAPI spec
Not disclosed
Claimed latency
Not disclosed
Status page
Not disclosed
Sandbox / test keys
Not disclosed
Support
Not disclosed
SLA uptime
Not disclosed
Preview brief
# Integration brief: Matchbook Exchange

Goal: build a feature on Matchbook Exchange data. Use only the official documentation below as the source of truth.

## Known facts (from SportDex, verify before relying on them)
- Website: https://www.matchbook.com
- Docs: https://www.matchbook.com/docs/api
- Sports: Multi-sport (40+)
- Data: Trading & risk, Odds
- Protocols: REST; formats: json
- Auth: bearer
- Free plan: none listed
- Note: Site blocked crawler; based on search snippets and third-party SDK pages. Exchange commission only, no plans published. Docs URL unconfirmed (from a third-party blog); auth type (session token) approximated as bearer. Country inferred.

## Verify before writing code
- pricing and request limits
- live update frequency
- whether commercial use is allowed on the plan you pick
- exact endpoint paths, parameters and response fields (read the official docs, do not guess)

## Implementation rules
- Keep the API key on the server (environment variable, backend route or edge function); never ship it to the browser.
- Cache responses and respect rate limits; count how many requests each screen triggers.
- Handle errors explicitly: invalid key, quota exceeded (429), missing fields, empty fixtures, timeouts.
- Start with one demo request and log the raw response before building UI on assumed field names.

Data quality signals

Data source & company

Official partners
Not disclosed
How data is collected
Not disclosed
Certifications
Not disclosed
Payment methods
Not disclosed
Minimum contract
Not disclosed
Country
United Kingdom
Founded
Not disclosed

Reddit · Hacker News · Stack Overflow · GitHub · YouTube

What developers say

Too little discussionalternatives

UK betting exchange with a REST API. No forum discussion, only GitHub: community wrappers in R and JavaScript, an MCP server for placing bets, and a few trading projects. A video describes the exchange as having lower commission than Betfair, interesting for US sports. No real feedback on API quality, limits or docs.

Praised for

  • Lower commission than Betfair per one video

Complaints

    Nothing specific.

    Our summary of public discussions, not a rating. Vendor posts are not counted as user opinion.

    Shortlist next steps

    Alternatives worth comparing

    • PolymarketBetting exchange67

      Prediction market exchange whose public Gamma API lists markets and events, including sports, without credentials; separate trading APIs and SDKs exist.

      Free tierMulti-sport (40+)
      Free tier52 discussions · 4.5k repos
    • SmarketsBetting exchange31

      UK person-to-person betting exchange offering a streaming trading API for order entry and market data, with an official Python client.

      ⚡ StreamingMulti-sport (40+)Football (soccer)Horse racing
      Price not public4 discussions · 38 repos
    • BETDAQBetting exchange29

      UK betting exchange whose webservice API is open to verified account holders for a one-off fee, and which offers a streaming commercial API to operators.

      Multi-sport (40+)
      from £250 one-time8 discussions · 3 repos
    • SX BetBetting exchange51

      Peer-to-peer crypto sports betting exchange with a public REST API for markets and orders and a realtime WebSocket feed for order books, scores and line updates.

      Free tier⚡ StreamingMulti-sport (40+)
      Free tier4 discussions · 77 repos
    • Betfair Exchange APIBetting exchange60

      Betfair's developer API for its betting exchange: market prices, order books and bet placement. Free delayed key for development; live key needs an approved application and a one-off fee.

      Free tier
      from £299 one-time30 discussions · 272 repos

    Evidence & transparency

    Official sources

    Facts were extracted from the provider's own pages on 2026-11-03. Empty fields mean the provider does not say, not that the feature is missing. How we know