← Blog · 📝 Article · 14 October 2026
FairBot Integration for UK Traders: Test Without Rate Limit Errors
FairBot connects to exchange APIs and the Stream API, and it can run automated strategies that also send Telegram alerts. The short version: update to FairBot 4.95 or later, gather your exchange credentials, create a Telegram bot through BotFather, choose API or Stream mode based on your latency needs, then run a small live test before trusting it with real stakes.
TL;DR:
- Telegram alerts work only after you start a chat with the bot; confirm its token has no extra spaces and posting permission is enabled.
- Choose Stream when strategies need fast price updates, since pushed market changes reduce repeated polling and lower the risk of shared API rate limits.
- Start each strategy on one market, inspect its activity log, and disable it immediately if its behavior deviates before applying it across matching markets.
- Test with a delayed key or the smallest stake, log rejected and skipped actions during short bursts, then gradually increase request volume after clean runs.
- Exchange API access may require separate verification, and an incorrect regional endpoint can cause authentication failures, so check both if connection attempts fail.
Table of Contents
- Setup prerequisites: what you need before you start
- Connecting FairBot to your exchange: API or Stream
- Building automation strategies, including Telegram alerts
- Rate limits, TOO_MANY_REQUESTS, and how to test without tripping them
- Troubleshooting common FairBot integration issues
- Our integration checklist: latency, verification and safe staking
- A practitioner’s view on automating lay strategies
- Where DonkeyRadar fits alongside FairBot
- FAQ
- Sources
Setup prerequisites: what you need before you start
Get these in place first, because half of all integration problems trace back to a missing credential or an outdated version.
- Run FairBot 4.95 or later: the Telegram action was added in that release, so check for updates inside the app before anything else.
- Hold an exchange account with developer or API access, or a broker account offering equivalent functionality.
- Decide between API-NG (polling) and Stream (push) based on how quickly you need price updates to act.
- Create a bot in Telegram’s BotFather and save the API token it generates somewhere safe.
- Start a chat with your new bot yourself. FairBot can only send messages to chats the bot has already been added to or contacted by.
With those four pieces ready, the actual connection takes a few minutes.
Connecting FairBot to your exchange: API or Stream
FairBot’s connection settings sit under one menu, and the choice between API and Stream shapes how your strategies will behave later.
- Open Tools → Options → Connection and enter your exchange credentials or connection token.
- Choose your mode: API-NG polls for updates on a schedule, while Stream API pushes market changes to FairBot as they happen, which suits strategies that react to fast-moving prices.
- If your account supports it, switch the connection location in settings to match your region’s endpoint for best results, since using an incorrect one may cause authentication issues.
- Save your settings, then watch the Grid or Ladder view populate with live prices before you enable any strategy. An empty grid after a minute usually means the credentials or mode are wrong.
- Confirm your account type supports API access. Some exchange accounts need separate verification before programmatic trading is unlocked, so check your provider’s documentation if the connection test fails repeatedly.
Pro Tip: Leave every strategy switched off during this first connection test. You only want to confirm that data is flowing, not that bets are being placed.
Once the feed is stable and prices are updating on screen, you are ready to build the logic that actually trades.
Building automation strategies, including Telegram alerts
Strategies in FairBot live in the Strategy Editor, and the structure is always the same: a rule, a condition, an action.
- Open Strategy Editor → Add Rule, then set the condition that should trigger it, such as a price movement, a time-to-off trigger, or a signal from an external source.
- Attach an action: placing or cancelling a bet, or sending a Telegram message. The Telegram action asks for your BotFather token once, then auto-detects the Chat_ID, and you can drop in variables like
{$MARKET_NAME}so each alert names the race or match it refers to. - Assign the strategy to a single market first. FairBot’s “apply to all” option will roll the same logic across every market that matches your filters, which is useful once you trust the rule but risky as a first move.
- Toggle the strategy on, then watch its activity log to confirm it is firing on the conditions you expect and not on anything else.
Disable a strategy the moment its behaviour looks even slightly off. Re-enabling it after a fix takes seconds; unwinding a bad run of automated bets does not.
Rate limits, TOO_MANY_REQUESTS, and how to test without tripping them
Exchange APIs cap how much you can ask for in a given window, covering concurrent requests, instructions per second and data-heavy calls like order and profit-and-loss checks. Breach those caps and you get a TOO_MANY_REQUESTS error, which typically means several request categories are sharing the same limited capacity rather than one call being uniquely at fault.
Switching to Stream mode cuts this risk substantially, since Stream pushes updates to FairBot instead of making it poll repeatedly for the same data.
A sensible testing protocol:
- Use a delayed key or your smallest available stake size for the first runs.
- Log every strategy event, including skipped and rejected actions, not just successful ones.
- Run short bursts of a few minutes each, checking logs between them.
- Increase frequency and concurrency gradually, only once a burst completes with no errors.
Design strategy cadence with this ceiling in mind from the outset: fewer, well-timed checks beat constant polling every time.
Troubleshooting common FairBot integration issues
Most problems fall into one of three buckets, and the fix is usually quick once you know where to look.
- TOO_MANY_REQUESTS: throttle your request frequency, switch to Stream where possible, and cut down on concurrent order or P&L checks running in parallel.
- No market data appearing: re-check your credentials, confirm the connection mode matches what your account supports, and verify you are running FairBot 4.95 or later.
- Telegram messages not arriving: confirm you (or the group) actually started a chat with the bot, that the token was pasted without extra spaces, and that the bot has permission to post in that chat.
- Unexpected strategy behaviour: open FairBot’s logs, disable the strategy immediately, and step back through the conditions one at a time before re-enabling it.
Our integration checklist: latency, verification and safe staking
We publish every lay signal before the race it applies to, and we track results publicly, so you can verify how an alert actually performed rather than taking our word for it. Measuring alert latency during a trial window matters just as much as the strike rate itself; a signal that arrives late is a different trade entirely.
We build our own workflow around three pillars: reliable delivery so alerts land when they should, conservative staking defaults while a strategy is new, and thorough logging so every automated action can be reconciled afterwards.
Pro Tip: Run any new FairBot strategy against our published signal history for a week before increasing stakes, so you are comparing automated behaviour against results you can already check.
A practitioner’s view on automating lay strategies
Automation rewards patience more than ambition. The strongest setups start small, log everything, and ramp stakes only after a clean run, because a strategy that looks sound on paper can still misfire against live prices in ways a quiet rollout will catch early and a rushed one will not.
— Donkey
Where DonkeyRadar fits alongside FairBot
Once your FairBot connection and strategies are tested, the remaining question is what feeds them. DonkeyRadar Free gives you daily lay signals at no cost, while DonkeyRadar Pro adds real-time alerts, full results history and API access for £29 per month, so a strategy you have built in FairBot can trigger directly off our published picks instead of a hand-picked list.
If you are still deciding whether lay betting suits your approach, our lay betting explained simply guide covers the mechanics before you automate anything. Start a trial and connect it to your FairBot setup at Donkeyradar.
FAQ
What is the difference between Betfair and Betfair Exchange?
Betfair runs both a traditional sportsbook and a separate Exchange product, where the Exchange lets customers bet against each other rather than against a bookmaker, including placing lay bets. FairBot and similar automation tools connect specifically to the Exchange side, since that is where the API and Stream data live.
Can you be restricted for winning too much on an exchange?
Exchange betting works differently from a bookmaker because you are matched against other bettors, so winning consistently does not get your account closed the way it might with a traditional sportsbook. Account restrictions tend to relate to suspected commercial or business-style usage rather than winning itself, so automation is best kept within personal-account terms unless you are pursuing a commercial route.
How do you place an accumulator on an exchange?
An accumulator in the traditional sense, where one stake rolls across several selections, is not a standard exchange bet type, since exchange markets are generally traded individually per event. Bettors wanting accumulator-style exposure on an exchange usually place and manage each leg separately, which is exactly the kind of repetitive task automation tools like FairBot are built to handle.
Is exchange trading profitable?
Profitability depends entirely on the strategy, discipline and risk controls applied, and no platform or tool guarantees a result. Transparent, verifiable track records, like publishing signals before results are known, give you a way to judge a strategy’s real performance rather than relying on claims alone.
Sources
- Sending Telegram Messages with FairBot | Fairbot
- Why am I receiving the TOO_MANY_REQUESTS error
- Betfair developers