• Intuitive and Customizable User Interface

    Choose one of three user interfaces for your betfair trading. Create your application workspace for trading on ladders, or for betfair bot execution.

  • Quick Navigation and Browsing Through Betfair Markets

    Create your favourite events to browse quickly for markets you want to trade on. Searching, sorting and filtering is supported across the entire application on any data.

  • Support for Trading on Multiple Markets Simultaneously

    Monitoring odds trend for chosen market selections and watching for current profit on open bet positions. Possibility to close bet position on a market selection, on entire market or on all open bet positions.

  • Trading Tools and Betfair Bots, Support for Automated Trading

    Placing dutch bets, closing a bet position on selection or on entire market. Be the firts in queue, Tick offset, Drip feeding, Trading bots, Trailing stop loss and more than ten other betfair bots. Tools for automated trading and betfair strategies.

  • Not yet betfair user? Get your free bet.

    Take winnings early or cut losses. Cash Out singles and accumulators. You're in control - you decide. Automatically get the best prices from The Exchange the moment you place your Sportsbook bets. Win or lose, we'll match your first bet with a free bet up to £50.

Welcome to betfair trading software.

Community Recent Articles

Community Recent Comments

  • Stefan
    23.3.2018 16:13:58

    Have a look at “Fill or Kill” bot parameter named: Odds. Read what description for this parameter says: “The odds you want to place your bet at. Set to 0 if you want to offer your bet at best offered odds.”

    What does it mean?

    Bot either places a bet at required odds, or offers bet. If there is no offer on back side and you asked to place Lay bet, then bot will waits till some offer appears because bot does not know at what odds you want to place a bet.

    Just to test bot functionality set your bot to place lay bet at 1.01 odds, and you will see that all works fine.

  • BBumber
    23.3.2018 15:36:42

    Yes, off course, in normal mode I'll be very limited regarding open markets. But even in normal mode it just doesn't cancel. I'm going to try the other way around and try to cancel in the associated market instead of placing. Thanks Stefan, this API settings info and refresh rates are very important to understand these behaviours.

  • Stefan
    22.3.2018 21:03:55

    Of course I tested it.

    You can open two instances of bfexplorer and do the same what you do with geeks toy.

    Actually if you open the market in bfexplorer and market is active then you will see bets even in one running instance of bfexplorer, because active market is updated immediately after you switch it to be active one.

    On markets with small liquidity and on markets where market data are not updated so frequently your bot can be executed with very big update time interval when market is in passive mode, because market data are updated really only when there some changes, this is the behavior of streaming api technology.

    If you switch to normal mode, then passive mode updates, and so bots execution is really executed each time set by update time interval for passive markets.

    Switch bfexplorer to streaming api, open market and watch for changes, on markets with small liquidity you can simply see that market shows no changes for minutes!

    So if you operate on markets with small liquidity then use normal mode, not streaming, but then you are limited to number of open markets you can monitor simultaneously.

    I hope you are able to use your common sense in this case.

  • BBumber
    22.3.2018 20:18:09

    I can only see the bets in the Geeks Toy software ladder. There is where I can cancel them manually. They don't appear in neither of the two markets "Market Orders / Bots" nor its BFExplorer ladders but they are well placed in the markets. It seems they're kept in some "Grey Area" where they're noit affected by automatic orders. I don't know hot to make videos, but I'll try to capture it with my phone camera or take some screenshots to try to illustrate what's happening. This is really weird. Have you tried yourself to place Fill or Kill bets in associated markets ? All works fine for you when BetMatchingTimeout is met ? Thanks Stefan 

  • Stefan
    22.3.2018 17:02:42

    Please make short video showing your problems, because what you say make no sense for me.

    When bet/s is/are placed on betfair market, the same way like market data are updated, bets are updated as well, I mean loaded to app model.

    So if you see bets on ladder, they are correctly loaded to market data, My Bets view is just other visual representation of your bets, like on ladders is another visual representation of the same market bets.

  • BBumber
    22.3.2018 14:40:59

    The strangest thing is that these bets don't appear in the "Market Bets" section of neither of the markets and therefore can only be cancelled in the ladder. This I cannot understand.

  • BBumber
    22.3.2018 12:40:18

    I believe I begin to understand (only a bit...) how your software and bots work, otherwise I wouldn't be able to have the profitable bots I have in the markets. But I know this is just the beginning and there's a huge mountain still to climb. In this case, the bot activates fine, but keeps in the market long after its BetMatching timeout is passed. I already tried with every combination of updating intervals, but there's something I'm missing here....

  • Stefan
    22.3.2018 11:50:05

    The “Fill or Kill” bot works fine, and it does not matter by which trigger bot it was executed.

    I already mentioned how a bot is executed on betfair markets, but it seems you do not understand it. Bot is a program/code but its execution time is limited to time when market data are updated only.

    Bfexplorer offers two types of market data updating, using streaming technology or simply calling api method for updated market/s at preset time interval, keep in mind that there are two update intervals, for active and for passive markets.

    When using streaming api to update market data, the data are really updated only when changes are detected on betfair servers, so it means even if you set your update interval for passive market to 10 seconds, you will not get updated data if no updates are made in 10 seconds interval on betfair servers.

    In such cases, betfair streaming api offers “heartbeat” so each 60 seconds there is triggered update procedure, so chance to execute a bot as well, but I implemented it only for monitoring active market, for passive markets bot is really executed only when there are detected changes on the market/s.

  • BBumber
    21.3.2018 21:55:16

    Yes, I think "Sequence Execution" may define it better. When a bot places a "Fill or Kill" bet on an associated market (without the InPlayKeepBet selected), the bet doesn't cancel when its BetMatchingTimeout is met. On the other side, when the same bot places the same Fill or Kill bet on its own market (not an associated market) the bet cancels when BetMatching timeout is met. Do you know why this happens and how to make it cancel (as it should) when BetMatchingTimeout is met ? Thanks Stefan 

  • Stefan
    17.3.2018 19:01:17

    This is more about understanding of English language:


    a series of things connected or following in succession: a chain of events.


    a continuous or connected series: a gruelling sequence of exercises.

    English is foreign language for me, so from your misunderstanding of the term: "Chain Execution", we can use following bot names, describing bot functionality:

    Execute Bots

    Execute Bots in Sequence (instead of using term: Chain Execution), or better: Sequence Execution?

Bfexplorer Statistics