listClearedOrders ... again

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • AlgoTrader
    Junior Member
    • Mar 2012
    • 243

    #31
    If all the we need is just to get a profit/loss for a market, then getMarketProfitAndLoss is preferable invocation.

    The only reason I think listClearedOrders is of interest are VOIDed bets. LAPSED/CANCELLED are out of interest, the bet that was not matched is alomost the same as the bet that was not placed. SETTLED bets are returned by listMarketBook
    Betfair Bots Made Easy

    Comment

    • Ipposnif
      Member
      • Mar 2014
      • 36

      #32
      Thx again Algo, but i need the P&L of each single bet because i provide a separate accounting for each strategy.
      So i renew the request to the "Betfair Creators Team" to provide an API similar to the old one 'getBet' for getting P&L and status of the bets using their unique keys.

      Comment

      • Guest

        #33
        Originally posted by gus View Post
        Yep, just noticed I've started getting clearedOrders again.

        Pity they're losers, but I don't suppose i can blame API-NG for that.
        Hey Guy

        Are you getting clearedOrders now ????

        Comment

        • gus
          Senior Member
          • Jan 2009
          • 134

          #34
          The last time I used it listClearedOrders it was getting the results eventually, but it was still desperately slow ... often 30 minutes or more after runners had been returned with status of WINNER or LOSER by listMarketBook and especially bad on Saturdays for Horse Races.

          S I've given up on it for now, and my apps now just keep a record of betSize and average matched price and calculate what the return should be as soon as there's a WINNER or a LOSER.

          i'd be interested to know if anyone else is managing to get the results via listClearedOrders reasonably quickly.

          Comment

          • Ipposnif
            Member
            • Mar 2014
            • 36

            #35
            I've made the porting of all the api functions with the exception of listClearedOrders (ex getBet).
            My application developing is blocked due this api is unusable and i still have to use the old getBet API to check my bets!
            It is unusable for several reasons:

            1) 6/10 times i make a simple request like the following:
            {"jsonrpc": "2.0", "method": "SportsAPING/v1.0/listClearedOrders", "params": {"betStatus":"SETTLED","betIds":["36918649542"]}}

            it goes repeatedly in timeout and sometimes i have this response:

            {"jsonrpc":"2.0","error":{"code":-32099,"message":"ANGX-0008","data":{"exceptionname":"APINGException","AP INGException":{"errorDetails":"Too many pending requests to cleared bet reporting service","errorCode":"TOO_MANY_REQUESTS","requestU UID":"prdang003-04251026-001e2caff8"}}}}

            2) There is an illogic thing in this function: i call this api to know mainly the status of my bets (and the P&L), why it needs to know from me the status of them (mandatory parameter betStatus).

            3) It is very slow (when it is on) to book the results, in USA races i have a delay of near 2 hours this evening.


            I read in this forum i'm not alone with these problems, please give us a report about this important api!
            Thank you

            Comment

            • Ipposnif
              Member
              • Mar 2014
              • 36

              #36
              The issues with api listClearedOrders seems resolved. The response time is now adequate also for the first call.
              Thank you

              Comment

              Working...
              X