User Comments

For betfair bot developers: Bfexplorer - Betfair BOT SDK

Setup your two “Place Bet” bots with parameters instructing the bot to place your bets when required odds conditions are met, and of course name your two bots settings.

Now you can use the bot: “Execute Bots” adding your two bot names to BotNames parameter. This way you will create a bot which will execute your “Place Bet” bots.

In the Add a new bot dialog you can find another bots used to construct your new bot by putting together more action bots, and names of these bots suggests how the action bots will be executed:

Execute on Selections

Execute Bots

Execute on Associated Market

Execute Till Target Profit

Execute Trigger Bot

If Then Else

Chain Execution

Concurrent Execution

Repeat Until

Different betfair events offer different market types. Therefore if you select the event type, and other filters are set as well, you can reload market types by clicking “Reload market types” button (This button is on the left under MATCH_ODDS text in your picture), so reloaded market types will reflect your current filter setting.

For tennis event there are quite a lot of market types, and set winner is flagged as: SET_WINNER. Such market type will Set 1 Winner, Set 2 Winner therefore if you are interested only for Set 2 Winner market you can filter such market by using grid view filters features, betfair api cannot filter only Set 2 Winner market.

I have just added multi value support for the GamesScore parameter. Install the latest version of bfexplorer.

SetsScore and PreviousSetGamesScore parameters accept multiple value entries, so sets separated by semicolon;

In your case you should set:

2 - 0;3 - 1;4 - 2;5 - 3;6 - 4;7 - 5;7 - 6

It means that if any of above scores is valid, an action bot is triggered. After an action bot is triggered by tennis bot, the tennis bot ends its execution, it means that an action bot is executed (bet is placed) only once.

Yes, it is correct setting for trading bot. When you use ProfitLossType parameter set to Percentage, the reached percentage value at which the bot closes its bet position is calculated from bet liability and not from odds/price percentage change. So if you set Loss to 50, and your liability is for instance 10 Euro, then your bet position is closed in loss when loss is greater than or equal to 5 Euro.

The 100% profit is never reached so you bot setting will close your bet position only when loss trigger is fired.

I would suggest testing bot settings, only your trading bot in practice mode, to learn how bot really behaves with your current bot settings.

Eduardo, forgive me but the subscription issue we already discussed many times.

You will get professional subscription paying more than for basic subscription only, if you cannot afford professional subscription, but for that I require active posting of articles or comments here on the bfexplorer forum, with at least some value for other bfexplorer users.

This web site is also my blog, as a software developer and of course as I actively trade on betfair, I post here ideas or just what interest me, and what have some relation to sports betting.

In this post I showed how I tested the oddschecker bot I develop for one user through freelancer. He wanted some manual for bfexplorer so with this article I showed him how to use bfexplorer.

I posted other articles last days, for instance about bettingexpert, and those ideas could be transformed to some bots or tools, but I need discussion about such ideas, and not what you say, what can be rephrased like:

Stefan will do/did a lot of work, and I will do nothing just try to use it and maybe I find my way to be profitable on betfair.

Bfexplorer implements betfair api methods for tennis live score, and by betfair T&C it covers only ATP and WTA matches. In the latest betfair news letter it was informed that Australian Open should be covered by betfair live score api.

On betfair web site you can see live score on ITF matches at the moment, so betfair have data feeds but cover live score through betfair api only for ATP and WTA. It would be possible to parse live score data from web pages as well, so bots could work with those data instead.

Problems you reported seems to be related to some problems on betfair api servers. I already explained that issue in my other article, and the problem is that none service on Internet is 100% reliable, you can see that on your screenshot that instead of bots are reporting score, there is missing data displayed in messages.

Anything bfexplorer does and presents is from betfair api, when a bet operation is executed and some error occurs on betfair server, related to this bet operation, the meaningful error message is displayed as well, for instance: ERROR_IN_MATCHER, LOSS_LIMIT_EXCEEDED and so on, betfair returns 17 different error messages for bet placing and 20 for update operations.

In the selected line there is error code returned from lower level of communication protocol, suggesting some problems with betfair api communication, so it means bfexplorer requested some bet operation on already placed bet, but this request was not processed by betfair api server.

Let me know you understand what I have tried to explain, because I am not quite sure what is your understanding of such applications working with api. For instance, one user told me that other betfair api app has better refresh rate because this app uses VPS.

I have just updated web site adding promised link to check subscription details:

http://bfexplorer.net/User/MySubscriptionDetails

I have just checked it, login with my brother’s account and all works for me on both exchanges.

Keep in mind that any betfair api subscription activation process is done on betfair servers. Once your betfair api subscription is activated is active till expires, and all necessary information are stored on betfair servers.

At the moment you login through api to betfair, your valid login session is used to retrieve any data you can see in bfexplorer app, and for any action you do on befair as well through bfexplorer app, that is clear I hope. If any error message is received by bfexplorer, or any other problem occurs when dealing with betfair api data, it is always a problem with communication through betfair api and betfair servers.

My authorization service is included only to the activation process when betfair api returns that your subscription expired, or you are a new user, a trial user, at this moment is activated your forum account on this web site as well.

I do not know what could went wrong with your login, but as bfexplorer displayed subscription dialog I think betfair returned data that you are no active subscriber anymore. In such cases my subscription activation services activates free limited access for bfexplorer (if such user is active on bfexplorer forum, what you are). So that is what probably you noticed, on the other hand my activation service do not generate new subscription code if expiration day is still in future date, so bfexplorer returned your old subscription code, that you tried again activate with a failure, and that is clear.

No service is 100% reliable, and that is what happened. Betfair api service were out of order for some short period maybe, or there was just some kind of malfunction in your Internet communication with betfair servers.

I do not think restarting bfexplorer or your computer had anything to do with your problem. Well, if a problem was with the Internet connection, or with your router/modem, so with a physical hardware, then switch on/off a computer or just restarting it could help.

I will add My Subscription Details menu to User menu on bfexplorer web site, so any user can check his/her subscription status.

Eduardo, links to betfair events/markets are created for betfair.com domain, so for international betfair users, and are valid. For instance, this link:

https://www.betfair.com/exchange/soccer/event?id=27641272

Is link to Real Real Madrid v Deportivo football match played Sat 09 Jan 8:30PM.

The above link is valid till betfair market is active, after betfair closes the event the event Id (27641272) is not valid anymore so clicking on above link returns 404 error message.

You are from Spain, with other jurisdiction rules for betfair. May I ask betfair users from other countries to check the above link?

There is only the new betfair API you can use, the old one had been retired.

Of course, till old web site allows you “legally” open and bet on some markets, then there is still possibility you could utilize such services and program yourself what you need, but you can spend on that significant amount of time just founding out that a day after you would done all necessary, betfair would cease old services/web sites.

You need an identity allowing you to bet or trade on betfair with no restriction.

Tyrion, unfortunately that is not an option for you. You can access through betfair api only those markets which are legally accessible depending on jurisdiction valid for your betfair account credential.

As an example of some restriction, just read this article: Betfair link does not work

Can you open the link, the Spanish user have problems to open?

I see, but then your question was misleading as well, I did not know that Romania’s jurisdiction prohibits to bet on Australian betfair markets.

For those betfairians without any restrictions, wanting to bet or trade on Australian markets, use “Connect to Australian Exchange” option in your login dialog, instead of to UK Exchange.

Yes, you can do so, please read the following article:

Australian Wallet/Markets

It seems that betfair changed event/market routine. I have just updated bfexplorer, install the latest version.

Happy New Year to All

When login to betfair select Connect to Australian Exchange and click on Login button, bfexplorer connects this way to Australian Exchange only.

You can run two bfexplorer instances when betting or trading on UK and Australian exchange.

Paul, bfexplorer (Professional) allows monitoring hundreds of betfair markets, therefore I did not implement any notification system as a core feature to the application user interface (UI) but instead such notification system is implemented by different bfexplorer bots.

This approach allows switching notifications on just for selected markets, well by executing a notification bot/s on such markets. Using bot executor tool you can automate this approach, for instance automatically open a race 10 minutes before race start time, and executing “Horse Racing Race Status” if you want to be informed about a race status.

Why I think is this approach better?

Well, you asked for market status notification changes (open, suspended, open in-play, closed), but someone else could ask for bet matching notification, or football/tennis score notification, and so on, you name it.

If such notification system had been built in the core application UI, then in the application setting I should add different settings for different notification systems. On the other hand a bot approach allows me to extend the bfexplorer features without adding new features to core bfexplorer backend, as bots or custom triggers are plugins/extensions.

I added video to your article showing how you can use “Horse Racing Race Status Bot”.

Yes, PreviousSetIndex set to 1 will evaluate the first set result.

Just think about it, and different possibilities you have got when using all parameters. You can set SetsScore for instance to 1 – 1, so now if you want you are able to setup a bot to trigger bot execution depending on how was played the first or second set.

Similar like for SetsScore, you can use more scores for PreviousSetGamesScore separating them by ;

The tennis bot must know which previous set should be evaluated, and that is set by parameter PreviousSetIndex.

A zero in a parameter value is generally used as not used bot parameter feature, and this approach is used through all bfexplorer bots.

You can use the tennis bot without requiring previous set feature, right? Or you can use the tennis bot without sets score, right? So not setting SetsScore, or leaving not valid value for PreviousSetIndex, switches off the parameter/feature evaluation.