Tweet
Hi,
I am experiencing the new Stream API, which looks great in principle. However, the devil is in the details and I just ran into a problem that currently obstructs my goal to migrate my bots to the Stream API.
The API provides detailed information about the unmatched bets, nearly identical to those returned by the API-NG. However, only the matched price and size are provided for matched bets, no placed date, even no betID. If the bet is matched when your bot is running, these info could be extracted from the previous unmatched orders (assuming you do not miss the message at the transition), but how could it be got from an initial image after reconnection or resubscription? Also, how will I be informed about the closing of a matched bet? Should I listen to the status of the corresponding market or is there a Stream API message with 0 matched bets when the bet is settled?
What is the recommended way to monitor the status of orders during their life cycle?
Regards,
Laszlo
I am experiencing the new Stream API, which looks great in principle. However, the devil is in the details and I just ran into a problem that currently obstructs my goal to migrate my bots to the Stream API.
The API provides detailed information about the unmatched bets, nearly identical to those returned by the API-NG. However, only the matched price and size are provided for matched bets, no placed date, even no betID. If the bet is matched when your bot is running, these info could be extracted from the previous unmatched orders (assuming you do not miss the message at the transition), but how could it be got from an initial image after reconnection or resubscription? Also, how will I be informed about the closing of a matched bet? Should I listen to the status of the corresponding market or is there a Stream API message with 0 matched bets when the bet is settled?
What is the recommended way to monitor the status of orders during their life cycle?
Regards,
Laszlo