Khanivore wrote: ↑Mon May 27, 2024 11:10 pm
Good news. An extreme measure to take but the error 406 disappeared after I did a full reset of Windows 11.
Back to a nice, clean setup!
foxwood wrote: ↑Mon May 27, 2024 2:13 pm
For a single instance of Bet Angel, the following settings have been tested and don't blacklist even when placing 200 bets per minute:
Bet Angel (200ms)
Matched & Unmatched bets (200ms)
Full market depth (200 ms)
Traded volume (1 second)
Guardian (200ms)
That's very useful to know, cheers for that man.
My settings are as follows
Bet Angel (200ms)
Matched & Unmatched bets (200ms)
Full market depth (200 ms)
Traded volume (1 second)
Guardian (200ms)
I still get the same problem, as below:
8/06/2025 17:41:23: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:23: Blacklist info:
LISTSELECTIONTRADES - Wait 59 seconds
18/06/2025 17:41:24: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:25: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:26: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:27: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:28: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:30: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:31: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:32: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:33: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:34: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:35: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:36: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:38: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:39: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:40: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:41: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:42: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:43: An error occurred while getting full market volume information for all runners: <406> BETDAQ cannot process your request as you are currently calling their servers too frequently and have been temporarily black-listed
18/06/2025 17:41:44: Blacklist info:
LISTSELECTIONTRADES - Wait 38 seconds
BETDAQ STATE AS FOLLOWS :
Betdaq Customer Service have alerted us to your mail regarding the blacklisting of your account due to excessive API calls, we have observed in our internal report from yesterday you are being blacklisted for the below calls.
This excessive call volume is again breaching your allocated API call limits, resulting in blacklisting events that temporarily suspend your ability to trade for 60-second intervals each time the threshold is exceeded.
Action Required:
Please urgently review and adjust the call frequency settings in your application — particularly the rate at which you are making the above Calls. Since you are using a third-party trading tool, we strongly recommend reaching out to the tool provider for assistance with configuration.
<MaximumRequests MethodNameSubstringsAndValues=
"PlaceOrdersNoReceipt=300;
PlaceOrdersWithReceipt=300;
ChangeOrderNoReceipt=300;
GetEventSubTreeNoSelections=50;
GetEventSubTreeWithSelections=50;
ListBootstrapOrders=50;
GetPrices=750;
ListOrdersChangedSince=310;
ListSelectionTrades=65"
Combined="1470" Any="300" />
Please take the necessary steps to stay within the allowed limits.
Thank you for your prompt attention to this matter.
The API Team
