listCurrentOrders misses some matched bets

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mr Magoo
    Junior Member
    • Jan 2011
    • 86

    #1

    listCurrentOrders misses some matched bets

    I've just started implementing the new API and have run into problems with this API call.

    To retrieve my bets, I have a choice of specifying EXECUTION_COMPLETE, EXECUTABLE or ALL, for matched, unmatched & both. The problem is, if I ask for just matched bets, the details of partially-matched bets are not returned.

    This seems like a bug to me. The old API would return details of partial matches. It doesn't make sense to me to ignore a matched bet if there's 1p remaining unmatched.

    The workaround is to always request ALL. However, this is horribly inefficient. I bet in a lot of markets and at any one point can have thousands of unmatched bets placed. So to discover the matched bets, this new API has to send me all of the details of the unmatched ones as well.

    Please fix this!
  • Mr Magoo
    Junior Member
    • Jan 2011
    • 86

    #2
    Also, it would be useful if listCurrentOrders could return more information on the bets, like the selection name and market name...

    Comment

    • Lopiner
      Junior Member
      • Feb 2009
      • 117

      #3
      Can anyone tell me please why does listCurrentOrders with the EXECUTABLE option for OrderProjection always returns less bets than i can see in my account under "Current Bets"? Also, when i ask for all the bets the number of bets is always smaller than my unmatched + matched bets.

      Thanks
      fooledbyabet.com

      Comment

      • VonWinning
        Junior Member
        • Oct 2014
        • 2

        #4
        Originally posted by Mr Magoo View Post

        The workaround is to always request ALL. However, this is horribly inefficient. I bet in a lot of markets and at any one point can have thousands of unmatched bets placed. So to discover the matched bets, this new API has to send me all of the details of the unmatched ones as well.
        I'm using the same workaround and always request ALL. If you set the "orderBy" parameter to "BY_MATCH_TIME", the orders without a matched date will be filtered out and you'll only receive partially and fully matched orders.

        Comment

        • API NG
          Junior Member
          • Aug 2014
          • 15

          #5
          ListCurrentOrders

          if I place un-match bet having persistence type = lapse at the time market goes inplay listcurrentorders doesn't return any bet in the markets. so how can we set bet is lapsed in our bot. before inplay market the bet was there having unmatch size. but after inplay its not cuming from anywhere I am send to from time range to = now and from now-30 days plz help me out

          Comment

          Working...
          X