← Blog · 📝 Article · 13 October 2026

Bet Angel Integration: 3 Signal Routes for Betfair Automation

Bet Angel Integration: 3 Signal Routes for Betfair Automation

The most reliable way to integrate Bet Angel with a signals feed is an API-driven pipeline that maps signal data to Betfair’s placeOrders endpoint, or Bet Angel’s own spreadsheet and native trigger inputs for a lighter setup. Excel/CSV piping and local middleware scripts both work as alternatives. Before building anything, gather your Bet Angel licence, Betfair app key and session token, and your signals feed credentials.

TL;DR:

  • Check that your Bet Angel edition supports automation, then obtain a Betfair app key, refreshable session token, and working credentials for the signals feed.
  • Start with spreadsheet or native triggers to verify signal mapping; move to a direct API pipeline only when you can maintain code and monitor failures.
  • Before live trading, use paper mode or small stakes, confirm a valid bet ID in listCurrentOrders, and log each signal timestamp against its bet ID.
  • A single API request has a maximum weighting of 200; after a timeout, check current orders before retrying to avoid duplicate bets.
Donkeyradar
donkeyradar.com
Connect Race Signals to Automation
DonkeyRadar publishes pre-race lay signals based on historical strike rates and live market prices for UK, Australian and US races.
Explore DonkeyRadar signals

Table of Contents

What you need first: accounts, keys, software and optional infrastructure

Before you connect anything, confirm your Bet Angel edition actually supports automation. Not every tier includes the automation and spreadsheet interfaces required for this kind of setup, so check your licence against Bet Angel’s own feature list before investing time in the build.

You’ll also need direct access to the Betfair Exchange API, which means registering as a developer, generating an app key, and knowing how to refresh a session token. The listMarketBook and placeOrders endpoints are the two you’ll use most: one for discovery and pricing, the other for execution.

Hardware demands are modest. A standard broadband connection handles most setups, though a low-latency VPS close to Betfair’s servers reduces delay if you’re running time-sensitive automation. Treat your app key and session token the way you’d treat a banking password: never shared, never hardcoded into a public script, and rotated if you suspect exposure.

Which integration methods work and when to pick each

Three practical routes connect a signals feed to Bet Angel, and each suits a different skill level and risk tolerance.

  1. API-driven pipeline: subscribe to a signals API, map each field to Betfair’s marketId and selectionId, then call placeOrders directly. This gives the lowest latency and the most control, but it demands comfort with code and ongoing maintenance.
  2. Bet Angel native inputs and Excel Link: use Bet Angel’s spreadsheet interface or built-in import triggers to feed signals in without writing a full integration. Setup is faster and requires little or no coding, though there’s a small latency cost compared with a direct API call.
  3. Middleware or bridge scripts: a local script receives signals and passes them to Bet Angel through its interfaces or straight to the Betfair API. This sits between the other two, offering flexibility for custom workflows without the full overhead of a bespoke API build.

Each method trades speed against simplicity. The API route wins on latency and auditability but needs someone who can maintain code and monitor for failures. The spreadsheet route is easier to set up and easier to inspect visually, which matters when you’re still trusting a new signal source. Middleware splits the difference, useful when you want custom logic (filtering signals by odds band, for example) without committing to a full rebuild of your execution layer.

Pro Tip: Start with spreadsheet piping to validate that your signal mapping is correct, then migrate to API automation once you trust the data flow.

A step-by-step checklist to connect a signals feed to Bet Angel

Work through these steps in order, and don’t skip the dry run.

  1. Install Bet Angel and confirm your edition supports the automation or spreadsheet features you plan to use.
  2. Register a Betfair developer app, copy your app key, and practise generating session tokens. Use listMarketBook to confirm you can pull live market data before attempting any order placement.
  3. Subscribe to your signals feed and confirm the delivery method works, whether that’s API, Telegram, or email alerts.
  4. Map each signal field, market ID, selection ID, side, and stake or liability tier, to the corresponding Bet Angel action, then configure your stake tiers to match.
  5. Run a dry run with small stakes or a paper-run mode. Confirm that placeOrders returns a valid bet ID and that listCurrentOrders shows the placement as expected.
  6. Turn on logging and reconcile every signal against Betfair’s order reports and your signal provider’s results history.

A few points are worth flagging as you go:

Once a signal fires and the bet settles, you still need an exit plan. Our guide on greening up a Betfair position and the six-step formula for trading out lay bets cover the part of the workflow that happens after entry, which matters just as much as getting the signal in correctly.

Common errors and Betfair API limits to design around

Betfair’s API returns specific error codes, and knowing them in advance saves hours of debugging. The Betfair error documentation lists the ones you’ll meet most often during integration work.

Every API request carries a weighting, and a single call has a maximum weighting of 200, which means poorly batched requests can hit limits faster than expected. Design your integration to respect concurrency guidance rather than firing requests as fast as your code allows.

Practical mitigations include batching requests where possible, using exponential backoff after a TOO_MANY_REQUESTS response, and passing a customerRef with every order so retries don’t create duplicate bets. Log every requestUUID and betId alongside the originating signal’s timestamp, since that’s the fastest way to reconcile a dispute later.

Automation benefits and how disciplined integration improves outcomes

Automation benefits and how disciplined integration improves outcomes — overview diagram

Automation doesn’t make a signal better, it makes execution faster and more consistent. The real gain from integrating Bet Angel with a signals feed is removing the lag and the hesitation that creep in when a human has to read a signal, open a market, and place a bet manually.

A data-first approach is exactly what a good integration should preserve: the discipline of the model, delivered without the delay of manual entry. If you want more detail on the mechanics, our automated lay betting guide covers risk rules and setup examples in more depth.

— Donkey

DonkeyRadar as a ready signals source for Bet Angel automation

We built our signals feed to plug straight into a Bet Angel workflow, not to sit as a separate research step you have to manually re-enter. Both the free and paid plans deliver signals in formats suited to automation, with additional features such as API access and alerts for readers who want faster, more complete integration.

Donkeyradar

Our paid subscription plan is priced as stated on our website, with a free tier available for anyone who wants to test signal delivery before committing to automation.

FAQ

What is Bet Angel integration?

Bet Angel integration means connecting the trading software to an external signals feed or data source, so bets can be placed automatically or semi-automatically rather than entered by hand. It typically relies on Bet Angel’s native spreadsheet inputs or a direct connection to the Betfair API.

Do I need coding skills to integrate Bet Angel with a signals feed?

Not necessarily. Bet Angel’s spreadsheet and native trigger inputs let you connect a signals feed with little or no coding, though an API-driven pipeline gives lower latency and more control if you’re comfortable building one.

What Betfair API errors should I expect when automating trades?

The most common are NO_APP_KEY, NO_SESSION, TOO_MANY_REQUESTS and TIMEOUT_ERROR, each documented in Betfair’s exceptions reference. Most are resolved by refreshing your session token, slowing request frequency, or checking listCurrentOrders after a timeout rather than retrying blindly.

How do I verify that an automated bet was placed correctly?

Check that placeOrders returned a valid bet ID, then confirm the bet appears in listCurrentOrders. Logging the signal timestamp alongside the bet ID makes it straightforward to reconcile against your results history afterwards.

Can I test an integration before using real stakes?

Yes, a paper-run or small-stake dry run is the recommended first step before scaling up. Testing your signal mapping with a spreadsheet first, then migrating to full API automation once the mapping is verified, reduces the risk of costly errors.

Sources