For smartbet.io tipsters the pick is automatically sent to your bot, fractions of a second after it has been submitted by the tipster.
For externally supported tipsters, the bot monitors your mailbox for incoming picks or pick notifications. Whenever such a message is found, it will retrieve the pick details either directly from the email or from a webpage in the case that the email contains a link to the actual pick details and not the actual pick itself. After the pick details are retrieved the corresponding order will be formed and sent to a book according to your settings.
To use the bot with externally supported tipsters you will need a subscription to the tipster that you are interested in and receive his original emails. Forwarded or not original emails are ignored.
The bot is using "clicks" for specifying the difference between advised odds and minimum odds. Clicks are equivalent to increments according to the table below:
The Pinnacle refresh rate specifies how often fixtures and markets are refreshed from Pinnacle. The default value of 240 secs means that it may take up to 4 minutes for your bot to see a new event or market. Note that the refresh rate does not affect bet placing speed, bets are always placed instantly.
For pregame events, markets change infrequently, so a large value such as the default of 240 secs will have no impact in most cases. In live events however, new markets can be added frequently in cases of a goal being scored or any drastic development in the game. If for example a goal is scored and Pinnacle creates the market "Over 3.5 goals" that did not exist before the goal was scored and a tipster that you are following makes a pick in this market before your bot refreshes the market from Pinnacle, your bot will report that the market was not found.
For this reason, if you are following tipsters that are placing many live bets or if you use the bot to manually place live bets you may need to consider a lower refresh rate for Pinnacle. The minimum allowed by Pinnacle is 5 secs, however it is not advised to use such a low refresh rate unless your turnover is really big.
A low refresh rate will result in a high data transfer rate with Pinnacle. Pinnacle's fair use policy states that API usage must be proportionate to wagering activity so the lower your refresh rate, the bigger your turnover must be.
Based on empirical data, you could safely use refresh rates down to 25-30 secs, provided that you place an average of 200-300 EUR worth of bets daily. A refresh rate of 25-30 secs would also mean that your bot would pick up a new market or event very fast, so you would be able to follow comfortably the vast majority of live picks.
Bet placement speed is affected by different factors depending on type of source. Specifically:
Picks from external sources are picked up by each user's bot by reading emails from the specified mailbox. This means that the primary factor that affects speed is the time it takes for an email to reach a user's mailbox. This in turn depends on the exact method that the sender is using to distribute emails (usually emails are sent in batches - not all in one try) and the latency between the sender's mail server and the recipient's mail server.
Additionally, even in the case that two users have email accounts in the same mail server and assuming that they receive the email at exactly the same moment, the email will not be picked up at the same exact moment for both, since each bot scans the user's mailbox in user defined intervals with the default refresh interval set to 1 seconds. This means that email scanning cycles between different bots will not coincide. Who gets the pick first will be mainly decided by chance for users with identical setup and settings.
Of course lowering the email refresh interval to 0 secs (each cycle starts immediately after the previous has ended) will yield a faster retrieval on average.
Picks from native sources are centrally processed and the corresponding orders are simultaneously created for all following bots. Still, from the moment that orders are generated until the moment that an order is sent to the bookmaker for execution there can be a time window of between 0 and 1 seconds for each following bot. This value will be different for every pick for the same bot and is mainly decided by the specific circumstances at the moment the order is generated, ie CPU and network load in the PC that the bot is running.
Theoretically, a more powerful CPU or low latency network connection would help in lowering the average delay, practically though they will not have a noticeable effect on bet placing speed, as the primary factor will always be circumstantial conditions.