Which Sports APIs Can Place Bets, Not Just Read Odds?
Odds feeds are read-only, so placing bets requires the API of the venue holding your account. In sports that means betting exchanges such as Betfair, Smarkets, and Matchbook, or prediction markets such as Kalshi and Polymarket. Each requires a verified account, its own authentication, and permission for your jurisdiction. Retail sportsbooks rarely offer bet placement APIs.
Why an odds feed cannot place a bet
An odds feed is a reader. It aggregates prices from many venues and returns them in one schema, which is what an odds feed is for. It does not hold your account, your funds, or a licence to accept wagers, so there is nothing for it to place a bet against.
Placing a bet requires an API run by the venue where the money sits. That venue authenticates you, checks your balance and jurisdiction, matches or accepts the order, and settles it. Very few venues expose that capability publicly, which is why the list of real execution APIs is short.
Two layers: data and execution
Most automated setups end up with two separate systems:
- Data layer: an odds feed or your own collection, used to find prices worth acting on.
- Execution layer: the venue's own API, used to read the live order book at that venue and send orders.
The join between them is the hard part. Event and market identifiers differ between the feed and the venue, so each opportunity must be mapped to the venue's own market and selection IDs. The feed's price is also only a hint. Before sending an order, read the price from the venue itself, because the feed may be seconds old. How to use an odds API covers the data side.
Betfair Exchange API
Betfair publishes the most established exchange API. Its Betting API covers market discovery, prices, and order operations such as placing, cancelling, and replacing orders, and its Stream API pushes market and order changes.
Access, per Betfair's developer documentation as checked on 2026-11-05:
- Every request carries an application key and a session token. Session tokens come from a login call, including a certificate-based login intended for bots.
- A delayed application key is free. Its prices arrive with a variable delay and some fields, such as traded volume, are not returned. It is for development, not live trading.
- A live key for personal use carries a one-off activation fee of 499 GBP, debited from the Betfair account once the key is activated. The account must be funded and fully verified, and Betfair expects testing to be done on the delayed key first.
- Software sold to other users needs a separate vendor licence.
Order requests accept a customer reference string that Betfair uses to de-duplicate accidental resubmissions, which matters when a network timeout leaves you unsure whether an order went through. The de-duplication window is 60 seconds, so a retry sent later than that is treated as a new order, which is the case worth handling explicitly. Account opening is restricted by country, so confirm Betfair accepts customers where you live before building anything.
Other betting exchanges
Smarkets and Matchbook also run exchanges with order-placing APIs. Matchbook publishes a public developer portal and states that any registered customer can start using the API immediately with their normal login credentials, authenticating with a session token and working within published per-minute rate limits. Smarkets documents an API covering market data and order management, placing, cancelling and updating bets, but gates access behind a request form, and its own Python SDK has been archived read-only since 2019, so community libraries are what is maintained. Their access conditions, rate limits, commission, and data redistribution terms differ from Betfair's and change over time, so read each venue's current developer terms directly rather than relying on third-party summaries. The practical questions are the same at every exchange: can your account use the API at all, what does live access cost, and what happens to orders when your connection drops.
Prediction markets: Kalshi and Polymarket
Prediction markets list event contracts, including many on sports outcomes, and their APIs are designed for programmatic trading. The prices read as probabilities, which prediction markets as a data source discusses.
Kalshi. Per Kalshi's API documentation, checked on 2026-11-05, trading requests are signed with a private key. Each request carries a key ID header, a millisecond timestamp header, and a signature over the timestamp, HTTP method, and path. Ed25519 is the default key type, with RSA-PSS supported. A demo environment uses the same signing process, which makes it a real sandbox. Kalshi operates as a US regulated exchange, and the legal status of sports event contracts has been contested by some states, so check current availability where you are.
Polymarket. Polymarket's documentation publishes a geoblock policy that applies to API orders as well as the website. As checked on 2026-11-05, it lists a small set of fully blocked regions and a longer close-only list that includes the United States and the United Kingdom for both the frontend and the API, and orders from blocked regions are rejected. Polymarket also runs a separately onboarded US product. Check the geoblock endpoint and the docs for the product you can legally use.
Event contracts are not bets in the sportsbook sense. They have their own resolution wording, fees, and order types, so a model built on sportsbook settlement rules needs adjusting.
What about sportsbooks?
Retail sportsbooks generally do not offer customers a public bet placement API. Automating a book's website or app usually breaches its terms and can lead to closed accounts and confiscated balances. Pinnacle was long the exception: its public API documentation states that the API has been closed to the general public since July 23, 2025, with bespoke access available by application for selected bettors, commercial partners, and research projects. If a book's own developer program does not document bet placement, assume it is not permitted.
A checklist before building execution
Answer these before writing order code:
- Legality: is the venue licensed or permitted where you live, and does it accept API trading from your jurisdiction?
- Account status: verified, funded, and approved for the access tier you need.
- Auth model: session tokens that expire, or signed requests with keys you must store securely.
- Sandbox: a true demo environment, or only delayed data with live money at the end.
- Order semantics: limit versus market behaviour, what happens to unmatched orders at in-play or at suspension, partial fills.
- Costs: commission, trading fees, and any access fee.
- Failure handling: idempotent order references, reconciliation of open orders after a disconnect, and a manual kill switch.
- Exposure limits: a hard cap enforced in your own code, independent of the venue.
Most production incidents come from the last two items, not from the model.
Frequently asked questions
- Can an odds API place bets for me?
- No. An odds API aggregates prices and returns them as data. It holds no account or funds and has no licence to accept wagers, so it cannot place anything. Placing bets requires the API of the venue where your account sits, such as a betting exchange or a regulated prediction market, and only where that venue permits API trading from your jurisdiction.
- Is the Betfair Exchange API free?
- Partly. Per Betfair's developer documentation checked on 2026-11-05, a delayed application key is free but returns delayed prices and omits some fields. A live key for personal betting carries a one-off 499 GBP activation fee after approval, and requires a funded, fully verified account. Software sold to other users needs a separate vendor licence. Exchange commission still applies to winnings.
- Can you trade sports contracts through the Kalshi API?
- Kalshi's API supports placing and managing orders on its listed contracts, which include sports event contracts. Trading requests are signed with an Ed25519 or RSA key, and a demo environment uses the same signing process. Availability of sports contracts has been contested in some US states, so check current terms and your location before building against it.
- Do DraftKings or FanDuel have a betting API?
- Neither documents a public bet placement API for customers, as of 2026-11-05, and automating either app is generally against their terms. Their prices reach developers through third-party odds feeds, which are read-only. Automated execution in sports is realistically limited to exchanges and prediction markets that publish trading APIs and permit access from your jurisdiction.