Who Can Get Pinnacle Odds Data, and Under Which Terms
A broker asks 10,000 USD up front and 100,000 a month per sport for an API on what it calls a Pinnacle white label.

Pinnacle does not offer an open sign-up API: its API page says access is by application.
A bettor who wants prices as data meets three limits: an application with no published criteria, a broker condition counted in thousands, and terms that bar collecting odds by automated means. A broker states a separate, numbered condition for an API on the account it calls a Pinnacle white label. Whether an application is worth sending depends on where you live.
- Source
- Pinnacle's API page, a GitHub README, broker help articles, operator terms
- Version
- Broker help articles updated 2026-07-22; API page undated
- Limit
- The application form was not opened
What does the Pinnacle API page say you must send?
The page presents a bespoke API product and says API access is permitted for both companies and individual customers. A form goes to a commercial team. The page lists what an application should contain: whether you are an individual or a company that might work with Pinnacle, whether you are currently a Pinnacle betting customer, your country of residence, the sports you want, the latency you need, and an overview of your project and how Pinnacle would be involved. For data partnerships with prediction markets it adds which markets or exchanges are involved, the countries of operation and the expected monthly trading volume. That list comes from the page itself. The interactive form was not opened or submitted for this page, so which fields are mandatory is unknown.
Three answers in the page's own FAQ set the expectation. Regional availability is decided from each customer's use case. Placing bets through the API is described as open to loyal customers, after a review of betting history. Cost is variable with the speed and breadth of access, and the page prints no figure. Academic research is named as a permitted use. A price, an acceptance rate or a waiting time quoted elsewhere does not come from Pinnacle's page. Why bettors want raw prices in the first place is the subject of the sharp betting guide.
A README with a date and no owner on the page
A repository on GitHub carries the API documentation, and its README says access to the API suite "has been closed for the general public since July 23rd, 2025". It adds that bespoke data services are offered to select high value bettors and commercial partnerships, that academics and pregame handicapping projects are supported, and that a funded account is required. Requests go by e-mail with a short description of the use case. The account behind the repository names Pinnacle in its profile and the repository points to Pinnacle's website, but Pinnacle's own API page does not link to it, so its ownership rests on indications.
Two facts keep the date from settling much. Earlier revisions of the README, from 2022 and from early July 2025, already told readers to contact Pinnacle for access, so the closure date does not show what stood open before it. The README and the official page also pull apart in tone, since one says select high value bettors and the other says individual customers, and no criterion is given. The date is best read as the README's own claim, because the official page says nothing about a closure and a dated sentence in a document Pinnacle does not cite is thin support for a sweeping statement. Pages that describe a public API do not cite a source for it.
Ten thousand up front, then a monthly bar
The only numbered condition for a broker-side API comes from BetInAsia's help center, in an article about an API connection on its PS3838 account. BetInAsia calls PS3838 a Pinnacle white label. The article, updated 2026-07-22, is addressed to a professional punter. It states a one-time fee in the form of a deposit of 10,000 USD, access to up to three sports, and a monthly turnover requirement of 100,000 USD per sport. If the requirement is missed, the deposit is forfeited and API access removed. There is no trial, and more than three sports means a form explaining intended commercial use. MadMarket's help center gives the same figures for its Probet42 product, in an article also updated 2026-07-22.
The article leaves gaps. It does not define turnover, so settled stakes, placed stakes, cancelled bets and lay bets are all open questions. It does not say whether exactly 100,000 meets the bar, or whether the 10,000 comes back if you leave. The wording "a fee in the form of a deposit" leaves open which of the two it is. The API guide it links to loads its content by script and could not be read.
Because the bar applies per sport, totals mislead. A punter on three sports at 150,000, 100,000 and 60,000 of monthly turnover totals 310,000, above the 300,000 that three sports call for, yet the third sport is 40,000 short and the 10,000 deposit is what is exposed. Two sports at 80,000 and 120,000 add up to 200,000, exactly twice the bar, and still fail on the first. A single sport at 99,960, from 833 bets averaging 120, misses by 40, and 834 bets would have reached 100,080. That reads as a product for a bettor already staking at that scale and a poor fit for anyone below it, because the forfeiture lands exactly where turnover falls short. This page does not suggest raising stakes to meet it.
A forfeitable deposit raises the stakes of BetInAsia's known weak point: public reviews describe withdrawals held in compliance reviews, with documents requested again and balances frozen meanwhile. MadMarket carries little independent track record and clauses that reserve the right to refuse, limit or cancel bets. Public reports of withdrawals held for weeks at AsianConnect come from a small sample, and Sportmarket is reported to ask for source of funds even after an identity check was accepted.
Where each Pinnacle API route stands, source by source
| Route | What the source says | Source and date | Evidence level | What is not said |
|---|---|---|---|---|
| Pinnacle, official API page | A form to a commercial team; cost and region decided case by case. | Pinnacle's API page, undated. | Read at source An operator statement. | Price, acceptance criteria, reply time, esports coverage. |
| GitHub README | Closed to the general public, bespoke services on request; dated by the README itself. | README of the API documentation repository. | Ownership unconfirmed Text read; the repository is not linked from any official page. | What the state was before the date; who is accepted. |
| BetInAsia, PS3838 account | Conditions for an API connection: a deposit, a cap of three sports, a monthly turnover bar per sport, no trial. | BetInAsia help article, updated 2026-07-22. | Read at source An operator statement. | Definition of turnover, treatment of the deposit on exit, content of the linked guide. |
| AsianConnect | Lists "Web / API / Mobile" as access methods for its Asianodds88 tool. | AsianConnect home page, undated. | Claim only The line was read; its content was not verifiable. | Documentation, terms, any link to Pinnacle odds. |
| MadMarket, Probet42 | The same deposit, sport cap and turnover bar as the BetInAsia article, for Probet42. | MadMarket help article, updated 2026-07-22. | Read at source An operator statement. | A documented link between Probet42 and Pinnacle; any API on other products. |
| Sportmarket | A customer API is not documented in the help pages read; its FairExchange page says API software bots cannot be used there. | Sportmarket help pages, undated. | Not verified An absence within the pages read. | Whether any API for customers exists. |
Dates are those the sources carry. "Undated" means the page shows no date or version.
What do the terms say about automated access to the Pinnacle API?
Every set of terms read points the same way. Pinnacle treats automated access as a matter for a written agreement, and BetInAsia and MadMarket bar scraping of their odds. The clauses below are quoted with their source and version, and methods and legal advice are left out.
Restricted
Pinnacle, terms v3.5 (CuraƧao and Malta versions) and version control 1.2 (Anjouan), clause 3, in a paragraph headed "Prohibited Scraping and Automated Access": the terms bar reaching the service or any API it makes available, "whether public or private", by automated means to collect odds, prices, lines or markets, unless "a separate written agreement" allows it. Its intellectual property clause also bars content being "merged with other data or published in any form".
BetInAsia, terms as archived in February 2024, clause 4.1.8, lists among forbidden uses "To scrape our odds". The live page could not be read, so whether the wording is current is unverified; check the terms in force.
MadMarket, current terms, clause 4.1.8 carries the same wording and clause 19.2 bars publication by scraping. A further clause reads "You agree not to use any automatic or manual device to monitor or copy web pages or content within the Service" (its sub-number was not noted).
The Fair Use Policy in the GitHub repository with the API documentation says commercial use and resale of the API need a written agreement, so granted access does not extend to passing data on. Pinnacle's terms, help pages and API page are silent on brokers, so whether an API held through a broker is covered is left open.
Keeping a price log by hand
The record you can source yourself is a log kept at the time of each bet, in a spreadsheet you own, from an account you are entitled to use. One line per bet: when it was placed, the book or account, the event, the market, the selection, the price taken and the stake. Beside it goes the closing price for the same market, copied by hand when the event starts, with the book it came from and the time you noted it. The source matters because two books close at different prices, and a closing figure without its origin cannot be compared later.
What the gap between your price and the close tells you, and what it cannot, is worked through on the page about closing line value, and how a price travelled between your bet and the close has its own page, on line movement. A hand log has limits of its own. It is slow, it records only what you bet, and the closing price depends on your attention at the start time. Exports from a broker help with the stake side and less with the price side, as the third question below shows.
Frequently asked questions
Does Pinnacle's API cover esports?
It cannot be confirmed. Pinnacle's API page says all its odds are available in the API product and that the feed can be limited to the sports you choose, but it does not name esports, and the public documentation behind this page has no esports entry either. Pinnacle does sell esports on its site, which is an inference about the feed. BetInAsia's article on its PS3838 API does not list sports.
Is there an official archive of past Pinnacle odds?
An official archive has not turned up in the sources behind this page, and a statement of absence only covers what was searched. Anything sold as an archive carries a provenance you would have to establish yourself, and the page does not say how Pinnacle's terms apply to a third party that gathered the data. The record you can source is the log you keep by hand, described in the section before this one, and the closing price it needs is explained under the closing-price test.
What does a broker account export contain?
BetInAsia's help article on its BLACK account describes an Orders view that lists bets by status with market, event, selection, back or lay, price, stake and profit or loss, an Accounting view, and Analytics with two presets covering the last 90 days plus filters for number of bets, stake, turnover, profit and ROI. The 90 days belong to those two presets. The article gives no maximum history, mentions no file export and lists no closing price, and it describes its Placed At column as the date and time of the match event, so that column cannot stand in for when you placed the bet. At Pinnacle, My Account shows betting and transaction history, and the help article says a detailed document can be requested from customer service by e-mail, with format and timing unstated.
Is the PS3838 API the same thing as Pinnacle's API?
The sources do not say. BetInAsia calls PS3838 a Pinnacle white label, yet its article sets out conditions of its own for an API connection, and Pinnacle's terms, help pages and API page do not mention brokers. Treat the two as separate routes with separate terms until a source ties them together, and read the page on what brokers charge and require before funding an account for any reason.