← Blog · 📝 Article · 17 October 2026
Geeks Toy Integration: Excel Runs Through Betfair, Not the App
Geeks Toy does not offer a native Excel add-in or a public SDK for external control, so there is no official way to drive it from a spreadsheet. If you need Excel or automation, use Betfair’s official Excel/VBA toolkit or build directly against Betfair API-NG or the streaming API. Check the relevant exchange documentation first to understand any limits on API calls.
TL;DR:
- Betfair’s official Excel/VBA sample needs your own application key and session token; it can list markets, retrieve prices, and place orders directly.
- Start with listEventTypes, listMarketCatalogue, and listMarketBook, then test responses in practice mode before using placeOrders or risking real funds.
- Use API-NG for order control and account or market requests; choose the streaming API when prices need frequent updates without repeated polling.
- A vendor bridge can reduce development work, but it adds latency, another failure point, and session handling outside your full control.
- Check Betfair’s API documentation for call limits, avoid unnecessary requests when tools share a connection, and consult Geeks Toy’s documentation for its current interface.
Table of Contents
- How does Geeks Toy connect to betting exchanges?
- Where do you change call rates and check API status in Geeks Toy?
- Does Geeks Toy work with Excel, and what are the alternatives?
- Which automation route should you choose: API-NG, streaming or a bridge?
- What is the step-by-step checklist for getting exchange data into Excel?
- How do you fix rate limits, latency and common mistakes?
- Why the technical detail matters for a lay betting workflow
- Stop looking for a Geeks Toy remote control
- Automate lay signals with DonkeyRadar
- FAQ
- Sources
How does Geeks Toy connect to betting exchanges?
Geeks Toy is a client of the exchange. It fetches market and price data and places bets through exchange protocols, then presents everything through its own interface: the ladder, staking tools and audio alerts. That interface is the product. It is not a public endpoint that other applications can call.
This distinction trips up many users. The exchange API is a set of services for market data, account details and order placement. Geeks Toy’s features are a human-facing layer on top of those services. One review of the software makes the same point: Geeks Toy has no native Excel integration or SDK for external automated control, and people often confuse the exchange access it uses with a remote-control API for the application itself.
The good news is that you do not need to control Geeks Toy to reach the exchange. Market, account and order access is available to developers directly through Betfair, with your own credentials.
Where do you change call rates and check API status in Geeks Toy?
When other tools share an exchange connection, check the relevant documentation for any call limits and ways to manage request volume. Avoid sending unnecessary requests, and consult Geeks Toy’s documentation for details about its current interface.
Pro Tip: Before running an Excel or scripted task, check the relevant documentation and confirm your exchange connection is working.
Does Geeks Toy work with Excel, and what are the alternatives?
Plainly: Geeks Toy has no built-in Excel integration and no SDK. Traders who need spreadsheets generally call the exchange directly. Betfair publishes an API-NG Excel toolkit and an Excel and VBA sample. You supply your own application key and session token, then run macros that navigate markets, fetch prices and place bets.
The Excel and VBA sample shows where the key and token go in the workbook and how to call API-NG from VBA, with examples for listing event types, market catalogues and placing orders.
Your practical options, in order of effort:
- Use Betfair’s official Excel toolkit and let it talk to the exchange directly.
- Build a small bridge that pulls selected data from the API and writes it into a workbook.
- Export snapshots from Geeks Toy for offline analysis, accepting that the data is static.
Pro Tip: Plan spreadsheet requests carefully alongside any other tools using the exchange, and consult the API documentation for guidance.
Which automation route should you choose: API-NG, streaming or a bridge?
Betfair’s developer documentation describes Exchange API-NG and the streaming API as the foundations for custom trading interfaces, market data access and automated strategies. They suit different jobs.
- API-NG: request and response calls for placing bets, reading account data and pulling market snapshots. Choose it for order control.
- Streaming API: a pushed feed built for low-latency market updates. Choose it when prices must stay current without constant polling. Our post on fixing silent streaming connections covers the pitfalls.
- Third-party bridges: vendor connectors that sit between a signal source and your trading software. They save build time but add latency, another moving part and session handling you do not fully control. Our Bet Angel integration guide shows how one works in practice.
Industry guidance is that traders needing tight spreadsheet-to-exchange links build against the exchange APIs rather than trying to control ready-made trading software such as Geeks Toy. If automation is the goal, start there.
What is the step-by-step checklist for getting exchange data into Excel?
Keep the first run small and deliberate. Follow this order:
- Obtain a Betfair application key and a session token, then enter them in the cells the Excel sample designates.
- Walk the request flow: listEventTypes, then listMarketCatalogue, then listMarketBook, and only then placeOrders. Use the provided macros or direct API calls.
- Test in practice mode, check that market and account responses look right, and move to real stakes only once the results match what you see on the exchange.
The official Betfair samples require you to supply your own application key and session token, and with them Excel can navigate markets, read prices and place bets by calling the Exchange API directly.
That requirement is a feature, not a hurdle. Your credentials stay yours, and the workbook talks straight to the exchange with no middleman. Our betting API guide for developers walks through the same flow from a build perspective.
How do you fix rate limits, latency and common mistakes?
Most integration problems come from three places: credentials, call volume and wrong assumptions.
- Authentication errors: recheck the application key and session token, and consult Betfair’s documentation for troubleshooting guidance.
- Rate-limit errors: review the exchange API documentation and adjust requests accordingly.
- Latency: consider the streaming API for market updates, as described in Betfair’s developer documentation.
- Common mistakes: assuming Geeks Toy exposes a control API, overlooking the exchange API documentation, and sending unnecessary requests.
Pro Tip: Change one thing at a time, such as how your script requests data, and check the relevant documentation to help identify what fixed the error.
Why the technical detail matters for a lay betting workflow
API access can help a publisher connect signals with exchange data. For information about DonkeyRadar’s signals and results, consult the publisher’s own materials.
For deeper examples, our exchange trading integration post covers the pillars of lay automation. Whatever you build, test it in practice mode before staking real funds.
Stop looking for a Geeks Toy remote control
Most advice on this topic starts from the wrong question. People ask how to wire Excel into Geeks Toy, when the better question is why you would. Geeks Toy is built for a human at a ladder. Trying to use it as a data server may require workarounds that could be affected by software changes.
The sturdier habit is to treat Geeks Toy as one client and the exchange as the real platform. Build your spreadsheet or bot against Betfair’s own APIs, give it its own session, and keep Geeks Toy for the manual trading it does well. When integrating tools, consider how their requests may affect one another, and consult the exchange documentation for guidance on managing API use.
What to do first: get your application key, run the official Excel sample against a single market, and watch the status window while it runs. Only then add automation, and only then think about live stakes. A careful, gradual setup can help you catch problems before they become costly. Resist the urge to automate everything on day one.
— Donkey
Automate lay signals with DonkeyRadar
If you are interested in automating pre-race lay signals, check DonkeyRadar’s materials for information about available APIs and integration guides. Start with DonkeyRadar Free, or read our Betfair lay betting strategy guide to see how the signals fit a workflow.
Try DonkeyRadar Free and see what the data says before the next race.
FAQ
Does Geeks Toy have native Excel integration?
No. Geeks Toy has no built-in Excel add-in and no public SDK for external control. For spreadsheets, use Betfair’s official Excel/VBA toolkit or call the exchange API directly.
Where do I change API call rates in Geeks Toy?
Consult Geeks Toy’s documentation and the exchange API documentation for information about managing requests when another tool shares your connection.
What do I need to run Betfair’s Excel toolkit?
You need your own Betfair application key and a session token. Enter both in the cells the sample workbook designates, then run the macros to browse markets and fetch prices.
Should I use the streaming API or API-NG?
Betfair’s developer documentation describes the streaming API and API-NG. Consult it to choose the services that fit your needs.
Sources
- betfair/API-NG-Excel-Toolkit
- Betfair APIs, Data and Tools for your use | Betfair Developers
- Guide to the Betfair Exchange API | Betfair Developers