8 Frequently Asked Questions
Q: Why are my bets still changing even after my order expired (or was cancelled)?
MollyBet only controls placement, the bookie controls the outcome of already-placed bets. That means we will stop placing new bets as soon as the order expires or is cancelled but already-placed bets cannot be un-placed.
Q: I've reached my credit limit. What can I do?
Talk to your agent.
Q: How can I withdraw my funds? I want to withdraw my funds!
Talk to your agent.
Q: Why does my async channel keep disconnecting?
To some extent this depends on the internet connection between your client and the MollyBet servers.
Alternatively, MollyBet may be forcing the connection to close because your client is too slow to read from the async channel.
If the server is unable to send data immediately over the connection, the data is temporarily queued to give your client the opportunity to catch up. If the client is too slow, however, the size of this queue increases indefinitely, and the client starts receiving more and more outdated information. When MollyBet detects a client is lagging significantly, it shuts down the connection.
Two criteria can trigger this behaviour:
there are more than 16,000 messages pending in the connection queue, or
the oldest item in the queue is more than 5 minutes old.
Q: Where are my MollyBet Accounting data from X months ago?
Due to the volume of data, detailed accounts are stored for about 3 months. After that you can see summarised statements using /statements.
Q: When does my MollyBet balance change?
A bet placement request will have immediate effect on the MollyBet balance - the balance is updated by subtracting the stake needed for the bet. Of course this needs to be extremely fast, as we don't want to miss the requested price.
Q: I'm trying to register to X events, but MollyBet won't let me. Why?
At this time, the default limit is 500 simultaneous events per MollyBet group at any one time.
As registration limits are enforced on a group by group basis, a different user (or another connection by the same user) may be using some of the quota.
Two connections registering to the same event both count towards the limit.
Q: Why do my bookies/account usernames look like "ab3c"?
This means that your agent has chosen to hide that information from you. While the codes are randomly generated for your accounts, they will be consistent.
Q: Why do I get the same data over HTTP and async when I create an order/betslip?
The TCP protocol guarantees that data will be received in the same order it was sent over the same connection, however the HTTP and async run over two different TCP connections. In other words, there is no way to guarantee that the HTTP call will return before or after the async message.
Q: Why do I receive an insecure (self-signed) certificate when connecting to the API?
If you get a self-signed certificate it probably means that your client HTTP/TLS libraries do not support the Server Name Identification (SNI) protocol extension, which is required in order to connect to the API.