2.30 fake

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Intrepid
    Junior Member
    • Sep 2012
    • 11

    #1

    2.30 fake

    the 2.30 fakenham win market doesnt return anything.
    the place market is ok, why could this be?

    this has happened on soccer where the odd market returns zilch
  • gus
    Senior Member
    • Jan 2009
    • 134

    #2
    looks ok here, but perhaps it's been fixed since.

    i don't know what it was like here at 12.01 when you posted

    Comment

    • Intrepid
      Junior Member
      • Sep 2012
      • 11

      #3
      still doesnt return anything


      ask=[{"jsonrpc": "2.0", "method": "SportsAPING/v1.0/listMarketBook", "params": {"marketIds":[1.116072680],"priceProjection":{"priceData":["EX_BEST_OFFERS"]}}, "id": 1}]



      ans=[{"jsonrpc":"2.0","result":[],"id":1}]


      if i change [1.116072680] to [1.116072681] it will return the place market correctly

      its definately a brain puzzler

      Comment

      • gus
        Senior Member
        • Jan 2009
        • 134

        #4
        Here's my (REST) query:

        https://api.betfair.com/exchange/bet...istMarketBook/ {"priceProjection":{"exBestOffersOverrides":{"best Pri
        cesDepth":1},"priceData":["EX_ALL_OFFERS"],"virtualise":false},"matchProjection":"ROLLED_UP_ BY_AVG_PRICE","orderProjecti
        on":"ALL","marketIds":["1.116072680"]}

        and part of the response:

        [{"marketId":"1.116072680","status":"OPEN","betDela y":0,"totalAvailable":35183.69,"bspReconciled":fal se,"numberOfActiveR
        unners":6,"version":847788698,"crossMatching":true ,"inplay":false,"numberOfWinners":1,"totalMatched" :39926.34,"complete"
        :true,"lastMatchTime":"2014-10-24T13:02:43.454Z","runners":[{"ex":{"availableToLay":[{"price":3.05,"size":48.47},{"price
        ":3.1,"size":131.55},{"price":3.15,"size":62.74},{ "price":3.2,"size":95.91},{"price":3.25,"size":300 .0},{"price":3.3,"si
        ze":39.63},{"price":3.35,"size":0.01},{"price":3.4 ,"size":74.0},{"price":3.5,"size":20.0},{"price":3 .6,"size":0.44},{"pr

        Comment

        • gus
          Senior Member
          • Jan 2009
          • 134

          #5
          think you may need quotes around the marketId?

          Comment

          • Intrepid
            Junior Member
            • Sep 2012
            • 11

            #6
            I will try, but cannot see why I should need quotes, as my appformats the ask request and it quite happily runs through every race except this fakenham race without the quotes

            Comment

            • Intrepid
              Junior Member
              • Sep 2012
              • 11

              #7
              many thanks Gus,


              your idea was spot on, but I hate it when I dont understand why.
              IT works 98 out of 100 without the quotes, and then suddenly i need the quotes, it a a puzzle

              Comment

              • gus
                Senior Member
                • Jan 2009
                • 134

                #8
                well, I have to admit I don't really understand it either.

                I'd have thought that, since the marketId is a String and includes a " . " it would always have to be in quotes and would never work without them, but I remember I had the same experience with eventTypeIds where I'd been using an integer instead of the required String for months with no probs, but changed it when I just happened to notice in the docs they were supposed to be Strings, and it still works fine.

                I suppose the API must be able to 'guess' most of the time but sometimes a particular number fools it.

                Comment

                • Fred77
                  Junior Member
                  • Jan 2009
                  • 37

                  #9
                  This keeps cropping up. Maybe a note in the documentation would help. Maybe if the API was stricter it would help.

                  If you provide a string then it will be interpreted as a string, if you provide a number it will be interpreted as a number. Depending on how you handle your variables / whether you use a JSON encoder etc for your requests, this interpretation may happen at either your end or at betfairs.

                  1.116072680 interpreted as a string is "1.116072680"

                  1.116072680 interpreted as a decimal number is 1.11607268 (note the trailing zero has gone)

                  Comment

                  Working...
                  X