Orbit Exchange API: How Automated Bettors and Bot Traders Access OrbitX (2026)
Orbit Exchange does not operate a standalone public API, but its Betfair liquidity infrastructure means the entire catalogue of established exchange trading software, betting bots, and API-driven automation tools available for Betfair also works for OrbitX markets. This guide explains how automated access to Orbit Exchange works, what software is compatible, what broker-level considerations matter, and how algorithmic bettors should think about the OrbitX API access model.
How Orbit Exchange API Access Works
Orbit Exchange is a white-label exchange product built on Betfair's market infrastructure. This means that the markets you see and trade on OrbitX share the same underlying liquidity pool and technical infrastructure as Betfair Exchange markets. The practical consequence for automated bettors is significant: the Betfair Exchange API (known as APING, or the Betfair Exchange API Next Generation) is also the access layer for Orbit Exchange markets.
Rather than learning a new API or rebuilding existing systems, traders who are already automated on Betfair can extend their access to Orbit Exchange markets by opening a broker account that provides API-level access to those same market endpoints. The position of the broker in this structure is to provide the account and funding layer, while the API interaction with the underlying exchange market operates through the Betfair infrastructure.
This architecture has both advantages and constraints. The advantage is that the vast ecosystem of Betfair API tooling, documentation, and community knowledge transfers directly to Orbit Exchange. The constraint is that you cannot access OrbitX via API independently of the Betfair API framework, and any changes Betfair makes to its API (versioning, rate limits, authentication) affect Orbit Exchange API access as well.
For the foundational steps to open an Orbit Exchange account via a broker, see our Orbit Exchange access guide and our Orbit Exchange registration guide for the complete account opening process.
The Betfair API structure relevant to OrbitX
| API component | Function | OrbitX relevance |
|---|---|---|
| APING (Exchange API) | List markets, place bets, cancel bets, stream prices | Core access layer for all OrbitX market operations |
| Streaming API | Real-time market data via WebSocket (low latency) | Essential for in-play trading bots on OrbitX |
| Historical Data API | Past market data for backtesting and model building | Available; covered under Betfair Historical Data service |
| Accounts API | Balance, funds, statement | Managed via broker account interface, not direct Betfair API |
For in-play automated trading, the Streaming API is the most important component. Unlike the polling-based APING which requires repeated requests to check for price changes, the Streaming API pushes market updates in real time via a persistent WebSocket connection. For a greyhound bot trading in 30-second races, or an NBA bot reacting to in-play scoring events, the Streaming API is the only viable approach. Using the standard APING polling at even 1-second intervals introduces too much latency for fast in-play markets.
Trading Software Compatible with Orbit Exchange
The ecosystem of Betfair API-certified trading applications represents the practical toolkit for non-developers who want to automate on Orbit Exchange without writing their own code. These applications connect to the Betfair Exchange API and can be configured to operate on OrbitX market endpoints.
Major trading platforms for OrbitX automation
| Software | Best for | Automation capability | Technical level required |
|---|---|---|---|
| Bet Angel Professional | Horse racing, football, multi-sport trading | Full bot builder, Guardian automation, Excel integration | Intermediate (no coding required) |
| Gruss Betting Assistant | Horse racing, greyhound automation | Trigger-based automation, Excel integration | Intermediate |
| Geeks Toy | High-frequency scalping, fast execution | Automations via add-ons; primarily manual with speed tools | Beginner to intermediate |
| Custom Python bot (betfairlightweight / flumine) | Custom strategies, statistical models | Full custom automation via APING/Streaming API | Advanced (Python programming required) |
| Custom Java bot (Betfair API SDK) | High-performance production systems | Full custom automation via streaming | Advanced (Java programming required) |
For the majority of exchange traders who are not software developers, Bet Angel and Gruss Betting Assistant cover most automation needs without requiring code. For bettors who want to deploy statistically-driven models, the Python ecosystem around the Betfair API (particularly the betfairlightweight library and the flumine framework) provides the most flexible foundation. Our exchange trading software guide covers these tools in more depth, including specific setup considerations and the learning curve for each platform.
Any automated system, regardless of how well the underlying model has been validated on historical data, should be run in a simulation mode for a minimum of 2 to 4 weeks before live deployment. The Betfair API includes a simulated betting environment (Betfair's test environment) that allows you to test order placement logic without real money. Additionally, most third-party tools (Bet Angel, Gruss) include paper trading modes. Subtle bugs in order execution logic, particularly around edge cases like market suspension during in-play events or concurrent order cancellations, are best discovered during paper trading rather than during a live session.
Broker Considerations for API-Level Access
Not all Orbit Exchange brokers provide the same level of API access, and this difference matters significantly for bettors who intend to use automated systems rather than placing bets manually through a web interface.
What to check before opening a broker account for API use
When evaluating brokers specifically for API and automated trading use, the key questions are:
- Does the broker provide direct Betfair API credentials? Some brokers offer a simplified proprietary interface that does not expose the Betfair API layer. If you need to connect third-party software like Bet Angel, you need direct API access credentials, not a wrapped proprietary API.
- Are there restrictions on automated betting in the broker's terms? Some brokers explicitly restrict automated or bot betting, particularly if they believe it creates disproportionate server load or gaming of commission structures. Read the terms carefully before deploying automation.
- What is the rate limit policy? High-frequency bots that poll price data multiple times per second may be subject to broker-level rate limiting on top of Betfair's own API limits. Confirm whether your intended use case falls within acceptable parameters.
- Is there dedicated support for API users? Technical issues with API access (authentication errors, connection drops, market endpoint changes) require faster resolution than standard account queries. Brokers with dedicated technical support for API clients are significantly more suitable for automated trading than those that treat all account queries uniformly.
AsianConnect88 ↗, our recommended broker for Orbit Exchange access, provides access to the Betfair API infrastructure alongside its standard web interface, making it suitable for bettors who want to operate both manually and via automated systems on the same account. See our AsianConnect88 review for the full assessment of their service offering.
Commission structure and bots
Automated systems typically generate higher trade volumes than manual betting, which interacts with commission structures in specific ways. On Orbit Exchange, commission is charged at 3% of net winnings per market. For scalping bots that open and close many small positions in the same market, the commission applies to the net profit across all those positions within that market, not to each individual trade. This is structurally favourable compared to a flat per-transaction fee model, and means that bots focused on net-positive market outcomes rather than raw trade count pay a predictable commission rate. Our Orbit Exchange commission guide explains the full commission mechanics and how they apply to high-volume automated trading.
Building a Custom Bot on the Betfair API
For bettors with programming skills who want to build their own automated systems, the Betfair Exchange API is well-documented and has an active developer community. The Python ecosystem is the most practical starting point for most developers.
Getting started with the Python ecosystem
The most widely used Python libraries for Betfair API development are:
- betfairlightweight: A lightweight Python client for the Betfair Exchange API that handles authentication, market listing, order placement, and streaming. Well-maintained and suitable for most use cases from simple bet placement to in-play streaming.
- flumine: A higher-level framework built on betfairlightweight that provides a structured approach to building betting strategies with built-in paper trading, logging, and simulation modes. Recommended for bettors who want to focus on strategy logic rather than API infrastructure plumbing.
Both libraries are open-source, actively maintained, and have extensive documentation and community examples. A developer with intermediate Python skills can have a working market-listing and basic bet-placement bot operational within a few days of starting with these libraries.
Key API operations for exchange trading bots
| Operation | API endpoint | Use in trading bots |
|---|---|---|
| listMarketCatalogue | APING | Discover available markets by event type, competition, date |
| listMarketBook | APING (or Streaming) | Current prices, available-to-back/lay, matched volume |
| placeOrders | APING | Submit back or lay orders (limit or market price) |
| cancelOrders | APING | Cancel unmatched orders; close in-play positions |
| replaceOrders | APING | Atomically cancel and resubmit orders at new price |
| Market Streaming | Streaming API (WebSocket) | Real-time price and order book updates for in-play bots |
The Betfair API session token expires after 12 hours if not renewed. For bots that run continuously (24/7 in-play systems, or overnight pre-game market systems), implementing a session keep-alive mechanism is essential. Without it, the bot will silently lose its authenticated session and stop placing bets without raising an error. The keepAlive API endpoint renews the session token for a further 12 hours. Call it from your bot once every 8 to 10 hours as a safe margin. Building this into your bot architecture from the start prevents mysterious failures during long-running sessions.
Why Profitable Bot Traders Prefer Orbit Exchange
Beyond the API access mechanics, the structural reasons why serious automated traders use Orbit Exchange rather than Betfair deserve specific consideration.
The Betfair Premium Charge is particularly punishing for successful automated systems. A systematic bot that generates consistent positive returns, even at modest margins, will accumulate the lifetime profitability threshold that triggers the Premium Charge faster than a casual manual bettor, because of its higher betting volume. Once triggered, the 20 to 60% levy on net winnings destroys the economics of most bot strategies that operate on thin edges. The full impact of the Premium Charge on algorithmic traders is covered in our Betfair Premium Charge guide.
Orbit Exchange charges a flat 3% commission on net winnings per market, with no Premium Charge overlay, no loyalty-based rate adjustments, and no retrospective levy on cumulative lifetime profits. For a bot strategy operating at a 5% ROI before commission, the difference between 3% OrbitX commission and 40% Betfair Premium Charge is the difference between a marginally profitable strategy and a structurally profitable one.
Additionally, Orbit Exchange via broker access provides no account restrictions on automated trading in the way that individual bookmaker accounts do. There is no maximum bet flag triggered by a consistent win rate, no account monitoring algorithm that reduces stake limits for identified systematic operators. The exchange model means your counterparties are other bettors, not a bookmaker's risk book, which removes the institutional incentive to restrict profitable systematic traders. See our exchange vs bookmaker guide for the full structural comparison.
Frequently Asked Questions
Orbit Exchange does not publish a standalone public API separate from the Betfair API. Because OrbitX operates on Betfair's liquidity infrastructure as a white-label exchange, automated access to Orbit Exchange markets is achieved via the Betfair Exchange API (APING). Third-party trading applications that are certified for the Betfair API, such as Bet Angel, Gruss Betting Assistant, and Geeks Toy, can connect to Orbit Exchange markets through this API layer. Access to those tools and API keys is typically managed via your broker account.
Yes. Betting bots and automated trading software can operate on Orbit Exchange markets via the Betfair Exchange API. The same API that powers automation on Betfair works for OrbitX markets. To use a bot on Orbit Exchange, you need: (1) a Betfair Exchange API application key, (2) an Orbit Exchange broker account that provides API-level access, and (3) compatible trading software configured for the OrbitX market endpoints. Not all brokers offer API access, so verifying this capability before opening an account is essential if automation is a priority.
Any trading software that uses the Betfair Exchange API can work with Orbit Exchange markets, subject to your broker configuration. The most widely used tools among Orbit Exchange traders include Bet Angel (comprehensive trading software with automation and bots), Gruss Betting Assistant (popular for horse racing and greyhound automation), Geeks Toy (low-latency execution preferred by high-frequency scalpers), and custom Python/Java bots built directly on the Betfair APING. Compatibility with the underlying Betfair API infrastructure is the key requirement rather than a specific integration with the OrbitX brand.
The Betfair Exchange API is free to access for non-commercial use up to a certain request rate limit. Commercial use or higher request volumes require a paid API subscription tier from Betfair. If you are building a commercial trading bot or operating at high request volumes, you will need to apply for an appropriate API access level. Your Orbit Exchange broker may also have specific terms regarding automated access that differ from personal manual betting terms. Always clarify API access conditions and any associated restrictions with your broker before building automated systems.
You do not need a personal Betfair betting account to place bets on Orbit Exchange, since broker accounts provide the access layer. However, accessing the Betfair Exchange API for development and testing purposes typically requires a Betfair developer account and API application key, which is a separate registration from a Betfair betting account. Some brokers that provide Orbit Exchange API access handle this infrastructure on the client's behalf, providing a simplified API endpoint that abstracts the underlying Betfair authentication layer. Check with your broker whether they offer a broker-managed API solution or whether you need to manage the Betfair API credentials directly.
Rate limits on Orbit Exchange API access are governed by the Betfair Exchange API rate limit framework. Standard access allows up to 1,000 API requests per hour for most operations, with lower limits for certain data-heavy endpoints (such as historical data requests). High-frequency traders and automated systems that require faster polling typically apply for elevated API access tiers. In practice, for the types of in-play trading bots and pre-game automation systems used by most serious exchange bettors, the standard rate limits are sufficient. Systems that require very high-frequency execution (such as scalping systems making multiple requests per second) may need to negotiate elevated access with both Betfair and their broker.