Community Articles
- Popular
- Recent
- Comments
-
Hello. Since yesterday I have a delayed API on my BF Explorer trading software. I had no bots running when this happened and now I am also unable to trade as all stakes in the markets keep flashing all over the ladders on random odds, being absolutely impossible to figure out what was the last price ...
9.5.2020 16:19:41 -
I tried BFexplorer, having used 3-4 different software applications beforehand. The 2 days utilising the software, I managed to get a feel for the product and like the modern display on the black background. Bets placed were very responsive with no lagging experienced from other products. A few ...
25.3.2015 17:55:00 -
Version 5.15.0927 The cumulative updates. Install from Bfexplorer Preview version. Version 5.14.0830 The cumulative updates. Install from Bfexplorer Preview version. Version 5.13.0818 The cumulative updates. Install from Bfexplorer Preview ...
27.9.2026 8:19:39
-
How I'm running Bfexplorer's MCP server on a Mac
I work on a Mac and use Claude Code to drive Bfexplorer through its MCP server. Bfexplorer is Windows-only, so it runs in a Parallels VM. Getting the Mac to talk to the MCP server took some trial and error, so here's what worked.1. Start Bfexplorer with the MCP flagThe MCP/REST server only starts ...
16.10.2026 12:01:36 -
I've just completed my week free trial and signed up to the Professional Monthly subscription plan but it still won't let me login with the API key I was given at
11.10.2026 13:08:00 -
Version 5.15.0927 The cumulative updates. Install from Bfexplorer Preview version. Version 5.14.0830 The cumulative updates. Install from Bfexplorer Preview version. Version 5.13.0818 The cumulative updates. Install from Bfexplorer Preview ...
27.9.2026 8:19:39
- by : Stefan
- by : Stefan
- by : Jimbo
- by : Stefan
-
API Key given at initial sign up at the free trial stage
by : quin2011 - by : layteruk10
Stefan
1)
“Close Market Bet Position” bot stops/cancels execution of all running bots on the market prior closing market bet position, and is clear why. The only exception is "Execute Trigger Bot", and of course is clear why. "Execute Trigger Bot" is custom bot, there are not known intentions how bots behaves and what bots are executed by this bot. It is trigger bot responsibility to ends its execution.
It means that in your bot solution, the “Close Market Bet Position” bot closes market bet position but your custom trigger bot still fires action bot execution anytime the trigger conditions are met.
So I believe that in your case you at least set for all your action bots the parameter AllowPlacingBetInPlay to False, what means that after the market is turned at in play all your action bots ends execution automatically, if they are in the state of opening bet position only.
The question is how you actually test your bots, because you did not mention this fact, you really do not know what you do.
I will add a new parameter to "Execute Trigger Bot": AllowBotExecutionTermination
2)
“Trailing Stop Loss on Market” seems to be a good idea, but my question is do you already understand how “Trailing Stop Loss” on selection works, because last time you asked about this bot, you were wrong.
Stefan
You already have SaveBotDataBotTrigger.
Stefan
Miro, all bfexplorer bots manage bet IDs to track only bet/s placed by the bot.
Your custom bot is developed as bot trigger, and bot trigger just orchestrates action bots, so if your bot trigger is programmed to manage bot/s bet position then it is able to do so, but that is not a general solution which could be done only when betfair would implement mentioned bet tagging, customerRef persistence through all relevant betfair api methods.
If you want to extend your custom bot trigger then all action bots derived from SelectionBot expose the property: BotBetsCache
So utilizing this BotBetsCache for all market, or selection bots, you would be able to calculate bet positions opened by individual bots.
Stefan
Betfair api does not offer feature allowing to tag bets:
http://forum.bdp.betfair.com/showthread.php?t=1898&highlight=customerRef
Bot Executor as the name suggests, just executes bots, bets and bet position is managed by bots.
Stefan
There is problem with gap detection, for now bot triggers action bot execution even if a gap is 1 tick only. In the code line:
if selection.GetOfferedPriceDifference() >= 2
the correct gap detection should be:
if selection.GetOfferedPriceDifference() > 2
Stefan
Do you actually understand what I said?
"Drip feeding bot" is already offered in bfexplorer, and I described how you can set it up.
What you propose to add is option to feed different size of bet stake, and I really cannot see any advantage in such bot feature, all the rest of features and “advantages” is already available in "Drip feeding bot" you can easy setup by using “Repeat Until” bot.
Stefan
Miro, there is no complicated chaining of bots. All you need is to set Place Bet bot, and then use “Repeat Until” bot to instruct the bot how you want to repeat Place Bet bot action.
Of course we all know what "drip feeding bot" main feature is, but I cannot see any advantage of your bot, there is no advantage in placing different stakes, so what bfexplorer already offers is efficient method to place big stake on a market.
“Repeat Until” bot offers 3 parameters you can use to set iteration type and timeout.
Stefan
I hope I will find some spare time in following days, will let you know when it is ready.
Stefan
What is an advantage for this kind of bot? Drip feeding bot can be constructed by using “Place Bet” bot and “Repeat Until” bot.
Read and watch: Base Bet Settings to Automate Trader’s Activity
Stefan
"Execute Till Target Profit" bot or "Execute Trigger Bot" are not stopped / canceled by "Close Market Bet Position" bot.
In your case the only option is to use "Execute Trigger Bot" custom trigger.
Stefan
Your problem is the connection latency to betfair servers. Yes, you can improve connection latency by using VPS which is located closer to betfair servers than your home connection to betfair servers.
On the other hand if you use VPS for manual trading you will get actually worse results, just think about it. You will get better results only when using automated betting solution with triggers/bots or automated trading solutions.
Stefan
Did you actually test your bot running and watched the bot behavior? I do not think so because Bet Status Description is just text not updated when bet condition changes. It shows initial bot status when bot status changes.
Execute the bot, and then report what you find out. I noticed it in many cases you just mislead others with wrong conclusions, please test bot behavior first before posting any comment or article to this forum.
Stefan
Miro, MinimumOddsDifference and MaximumOddsDifference parameters are used before a bet is placed. If you set these parameters and values are not met then your bet is not placed.
If you do not want to use the chase odds feature which is actually one of base features when you use calculated odds bet placing, so when PlaceBetInAllowedOddsRange is set, then set ChaseOddsTimeout parameter to 1 day for instance: 1.00:00:00. This setting will effectively stop bet updating, as your bet is active on greyhounds market just for couple minutes.
Stefan
Miro, your custom bot script had been developed without supporting StakeType parameter. Actually when your bot script was developed such bot parameter (StakeType) was not offered by bfexplorer bots.
After I finished your custom bot I sent you the source code as well, so just have a look on function: ToObjectValue, if you want to add support for StakeType then add it to this function.
Stefan
Miro, there is actually no problem with this bot, when bot is executed with PlaceBetInAllowedOddsRange, and you set required parameters for MinimumOddsDifference and MaximumOddsDifference, then initial bet is placed only when those parameter values are met, so the bot will do exactly what you want to.
Once a bet is placed, and if it is not fully matched, then bot updates bet odds to fulfill your requirements for bet placing at required calculated odds, but in this process the MinimumOddsDifference and MaximumOddsDifference parameters are not used, these parameters are used only for initial bet placing.
If you require other bot behavior in this stage (when bot updates odds), then of course a custom bot must be programmed, but you did not mentioned such behavior.
Stefan
It is clear that bot parameters setting have influence on bot behavior when placing bets, and that bet is always placed at some odds (0 is not valid odds), so set PlaceBetInAllowedOddsRange to true, and OddsDifference parameters to required values, then your bot will place a bet when OddsDifference parameters are in preset range. The default value for Odds range is 1.01 to 1000.0, so bet is placed at odds calculated by using the current offered odds, and of course reflecting all other Bet Attributes parameters setting.
Stefan
There is no support for entry criteria to be read from CSV file, on the other hand you can develop your custom bot or bot trigger, so then your bot will use whatever features you will program to betfair bot.
Stefan
You did not set PlaceBetInAllowedOddsRange parameter, therefore your bet was placed at exact odds, initially set to the Odds I described. If you wanted to place your bet in allowed odds range then why you did not set the parameter: PlaceBetInAllowedOddsRange?
I do not know what is your use case scenario for PlaceBets bot? You can simulate such behavior by using Place Bet bot and Execute on Selections bot.
Stefan
You did not set the parameter PlaceBetInAllowedOddsRange and Odds is set to 0, what means your bot should place a bet at Odds 0, right?
In such cases bot sets Odds parameter to the current odds depending on the BetType (so Back in your case, and as OfferMyBet was set to True, the Odds was set to current offered lay price) when the bot was executed.
Stefan
Man, SET_WINNER attribute includes all Set Winner markets, so 1, 2, and 3, 4, 5 if such markets are open during a match by betfair. SET_WINNER attribute is not something I have introduced myself to bfexplorer, it is the attribute offered by betfair api to filter markets.
Bet Event or Bet Event Trader offers Markets toolbar button if you click on this button, all associated event markets are showed, that is the second way how you can open any associated bet event market.