← Blog · 📝 Article · 23 October 2026
Betfair Tipster Integration: How to Connect Signals Safely
Betfair tipster integration means getting a tipster’s selections into your Exchange account without retyping them. In practice you have three routes: place bets by hand from a dashboard link, import the tips into automation software, or pull them through an API. Which one suits you depends on how many bets you place, how fast prices move, and how much you trust the tipster’s numbers. This guide covers all three, the technical limits that trip people up, and how to check a tipster’s record before any money goes on.
We publish lay signals for UK, Australian and US racing, so we write from the point of view of a service that has to be integrated. Where we describe general method, it applies to any tipster, including us.
TL;DR
- There are three routes: manual placement from a link, import into bot software (CSV, URL or direct feed), or API access to build your own.
- Whatever you choose, run one automation engine per Betfair account. Tools share the same API connections and can collide.
- Watch the Betfair API limits: 200 markets by default on a stream subscription and a cap on login requests per minute.
- Never trust a self-reported spreadsheet. Check that selections were time-stamped before the race and are available at prices you could actually get.
- Paper-trade any new tipster for a few weeks before you stake real money.
Table of Contents
- What integration actually involves
- Route 1: manual placement from a dashboard link
- Route 2: importing tips into automation software
- Route 3: building on the API
- Verifying a tipster before you connect anything
- Our view on integration
- Where DonkeyRadar fits
- Choosing a data source for racing research
- A sensible set-up, step by step
- FAQ
- Sources
What integration actually involves
A tipster gives you a selection: a horse, a race, a price or a price range, and often a staking level. Integration is the step that turns that line of text into an order on the Exchange. Three things have to match: the market (which race), the selection (which runner) and the instruction (back or lay, at what price, for what stake).
Most of the pain comes from the first two. Betfair identifies a market with a market ID and a runner with a selection ID. A tip that says “Horse X, 14:20 Kempton” has to be mapped to those identifiers before software can act on it. Good tools do the mapping by name and time. Weaker setups rely on you doing it.
The Betfair App Directory lists automated betting software that can import tips from external sources, including files, URLs and direct feeds from data providers. That is the mainstream route for people who want bets placed without sitting at a screen.

Route 1: manual placement from a dashboard link
The simplest integration is no integration. The tipster publishes a signal, you click a link that opens the right market on the Exchange, and you place the bet yourself.
This suits you if:
- you place a handful of bets a day;
- you want to judge the live price before committing;
- you do not want software holding your account session.
The weakness is speed and discipline. Prices on a racing market can move quickly in the final hour, and a signal you see ten minutes late may no longer be worth taking. Manual placement also invites second-guessing: skipping the signals that feel wrong is the fastest way to destroy a statistical edge.
Our own dashboard works this way by default. Each signal comes with a direct Betfair Exchange link and a staking tier grade, so you land on the right market and know the intended stake size.
Route 2: importing tips into automation software
This is the route most people mean by “Betfair tipster integration”. You run dedicated betting software on your own computer or a server. It reads a tip source, matches each line to a market, and places the bet when your conditions are met.
Typical import sources are:
- A CSV file. The tipster or you export selections in a fixed column layout.
- A URL. The software polls a web address that returns the day’s selections.
- A direct provider feed. The tool connects to a data or tipping provider natively.
Choose by workflow, not by feature list
An industry comparison of two popular tools makes a useful point: the better choice depends on how you work. If you want to set rules and leave them running, a bot-style tool fits. If you also trade manually from a ladder and want automation alongside, a full trading terminal fits better. Comparing on “bot features” alone favours the first type, and comparing on in-play scalping favours the second.
For lay signals on pre-race markets, you rarely need a ladder. You need reliable import, a sensible staking rule and a price check. We cover the routes for a trading terminal in our guide to three signal routes for Betfair automation.
The CSV trap
CSV import fails more often than any other method, and usually for a boring reason. Spreadsheet programs love to “helpfully” reformat data. A market ID that contains a decimal point can be turned into a number or a date, and then the software cannot match your tip to the right market.
The Bf Bot Manager support forum states that tips can only be imported from a textual CSV file, not a native Excel workbook. Practical rules:
- Save as CSV, not XLSX, and open the saved file in a plain text editor to check it.
- Format ID columns as text before you paste anything in.
- Keep the column order exactly as the software’s manual specifies.
- Test with one or two selections before loading a full card.
If a tip does not fire, the file is the first suspect, not the tipster.
One engine per account
Betfair allows a limited number of simultaneous API connections per account. Running two automation tools at once means they compete for those connections. The same BotBlog comparison notes that this can cause missed bets, delayed updates and error spikes, and that experienced users dedicate one primary automation engine to each account.
The practical rule is simple: if you already have a tool open for trading, do not start a second one for tips. Route the tips into the first one.
Route 3: building on the API
If you write code or use trading software that accepts external instructions, an API feed is the cleanest integration. The signal provider sends structured data, your software reads it, and nothing passes through a spreadsheet.

Our Pro plan includes API access for exactly this purpose. Our guides to the Betfair Streaming API and a wider betting API guide for developers go into detail on the build side.
Limits you will hit
Betfair’s API is protected by rate limits, and they are not decorative. According to a Betfair developer forum thread on request limits, operations such as listMarketBook are restricted in how many concurrent requests they allow, and exceeding the limits returns errors rather than slower responses.
Two limits matter most for tipster integration:
| Limit | What it means | What happens if you exceed it |
|---|---|---|
| Login requests | More than 100 successful logins in a minute is too many | A temporary ban on new sessions |
| Stream subscriptions | The default limit is 200 markets | A subscription error and no new markets |
The forum answer also clarifies that the subscription count is evaluated at the time you subscribe, so you should not assume a closed market frees up room in your head-count. Limits tend to attach to the account rather than a single tool, so every program you run on that account draws from the same pool.
A sensible habit: subscribe only to the markets that carry a live signal, not to the whole day’s racing. A lay signal strategy usually needs a few markets at a time, not hundreds.
Reading prices without betting
Some developers worry that fetching market data with a live application key, without placing bets, will get the key restricted. Betfair earns its money from commission, so it expects real betting activity. A developer forum reply on read-only queries says that, as long as you are placing bets overall, you do not need to bet on every market you query. This is a forum answer from 2020, not a Betfair policy statement, so check the current terms for your own key.
Verifying a tipster before you connect anything
Integration makes it easier to lose money quickly. Automating a tipster whose record is invented just loses it faster, so verify first.
What a trustworthy record looks like
A self-reported spreadsheet or a screenshot proves nothing. TipsterCheck explains that screenshots and spreadsheets can be edited, and that losing selections can quietly disappear. The same guide describes independently captured results as those recorded before the event by someone other than the tipster.
Use this checklist:
- Time stamps. Was every selection logged before the race, with the time recorded?
- Completeness. Are the losers there, in order, with no gaps in the sequence?
- Price basis. Is each result settled at a price you could realistically have taken?
- Sample size. Is there enough history to separate skill from variance? We discuss this in spotting real edge across 500 bets.
- Permanence. Can you still see old results, including the bad weeks?
We go through the full process in our eight-step audit for tipster proofing and in our guide to tracking your betting results.
The unachievable price trap
This is the most expensive mistake in tipster following. A tipster can show a high strike rate on paper while quoting prices that existed for a moment or that you could never match on the Exchange. TipsterCheck flags this unachievable price problem as a central pitfall: the follower’s real profit ends up far below the headline figure, or disappears.
For lay betting the trap has a particular shape. When you lay a horse, you are the bookmaker. You need someone to back at the price you want, and on thin early markets there may be nobody. A signal that says “lay at 6.0” is worth nothing if the market only offers 7.2 by the time you look. Always compare a signal’s stated price with the depth you can actually see.
Paper-trade first
The same guide recommends a simple discipline: record every selection the moment it is posted, at the price you could realistically have taken, and keep the losers in. After a few weeks you have an honest return figure that owes nothing to marketing. It costs nothing and takes ten minutes a day.
With a free signal tier, you can do this properly. Log the signals, check them against the live market, and only then decide whether to automate.
Our view on integration
We build signals, so we see both sides of this: what a provider has to publish, and what a bettor has to do with it.
Our position is built on three practices:
- Publish before the race. Every signal appears before the off, so nobody can claim it was added afterwards.
- Record everything, permanently. Wins and losses both go into the public results history. Losses happen. Transparency is the whole point.
- Selection by statistics, not opinion. Our algorithm combines historical strike rates with live market prices to find the runner most likely to lose.
We would add one piece of advice that does not flatter any provider, us included: automate last. Start with manual placement, learn how the Exchange behaves around your chosen races, and only then hand placement to software. Most integration disasters come from people who automated before they understood the market.
If you are new to the strategy itself, our Betfair lay betting strategy guide and the plain explanation of how lay betting works come first. The lay betting calculator helps you size liability before you connect anything.
— Donkey
Where DonkeyRadar fits
The free tier gives you daily lay signals, which is enough to paper-trade and check our results history for yourself. Pro costs £29 per month after a seven-day trial and adds real-time alerts by email and Telegram, the full results history and API access for trading software. The dashboard carries direct Betfair Exchange links and staking tier grading on every signal.
You can start on DonkeyRadar without paying anything and move up only if the record convinces you.
Choosing a data source for racing research
Readers often ask which racing data and analytics sites are worth using alongside a tipster. Rather than rank them, here is what to look for:
- Price history. You need to see how a market moved, not only where it finished. Our guide to racing odds comparison sites for UK lay bettors covers this.
- Exportable data. If you cannot export it as clean text, you cannot automate with it.
- A visible track record for any model or rating. The same checklist applies as for tipsters.
- Software options. Our roundup of horse racing tipster software compares tool types by what they do.
For lay-specific methods and typical UK approaches, see our UK lay tips guide.
A sensible set-up, step by step
- Paper-trade for several weeks. Log signals, time-stamp them and record the price you could really have had.
- Place bets manually from dashboard links for a while. Learn how liquidity behaves on your races.
- Choose one automation tool that fits your workflow, and keep it as the only engine on your account.
- Test the import with a single selection. If using CSV, save as text and check the file in a plain editor.
- Set a staking rule and a maximum liability per race, and do not override it on instinct.
- Keep API usage lean. Subscribe to the markets with live signals, not the whole card.
- Review monthly against the public results history. If your outcomes drift well away from the published record, find out why: usually it is price slippage or missed bets.
FAQ
Can I connect a tipster to Betfair without coding?
Yes. Several automation tools accept tips by CSV file, URL or a direct provider feed, and you configure them through settings rather than code. You can also skip software and place bets from a link on the signal. Coding only becomes necessary if you want to read signals through an API.
How do I verify a tipster’s results?
Look for results that were recorded and time-stamped before each event, with every loser included and prices you could actually have taken. Do not rely on screenshots or spreadsheets the tipster controls. Paper-trade the selections yourself for a few weeks to calculate your own return.
Why did my imported tips not place any bets?
The most common cause is a damaged CSV, often because a spreadsheet changed ID columns into numbers or dates. Save the file as text, check it in a plain text editor and test with one selection. The next suspects are a second tool competing for your API connections and a price condition that the market never met.
Does DonkeyRadar offer Betfair integration?
Our dashboard gives direct Betfair Exchange links for every signal. Pro adds real-time email and Telegram alerts and API access for connecting signals to trading software. The free tier lets you follow the daily signals and check the results history first.
Is lay betting suitable for everyone?
No. Laying a horse exposes you to a liability larger than your stake, so work out the maximum loss before every bet. Betting is for over 18s only, and if it stops being fun, GamCare offers free support on 0808 8020 133.
Sources
- Bf Bot Manager, Betfair App Directory
- BFBM vs Bet Angel, BotBlog
- Importing horses from an Excel file, Bf Bot Manager forum
- TOO_MANY_REQUESTS: clarification of limits, Betfair Developer Program Forum
- TEMPORARY_BAN_TOO_MANY_REQUESTS on login, Betfair Developer Program
- Stream API subscription limit, Betfair Developer Program Forum
- Read only query, Betfair Developer Program Forum
- Fake Tipster Results Explained, TipsterCheck
- Verified vs Unverified Tipster Results, TipsterCheck