Empty TotalMatched

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • komposter
    Junior Member
    • Mar 2015
    • 17

    #1

    Empty TotalMatched

    Hi all!

    I experience some problems with listMarketBook request.
    I tried to receive data from single tennis match (running now) and it works. But totalMatched fileds for each player are empty (summary totalMatched for whole match is right):

    My request:
    Code:
    [{"jsonrpc": "2.0", "method": "SportsAPING/v1.0/listMarketBook", "params": {"marketIds":["1.117592185"],"priceProjection":{"priceData":["EX_BEST_OFFERS"]}}, "id": 1}]
    Server response:
    Code:
    [{"jsonrpc":"2.0","result":[{"marketId":"1.117592185","isMarketDataDelayed":true,"status":"OPEN","betDelay":5,"bspReconciled":false,"complete":true,"inplay":true,"numberOfWinners":1,"numberOfRunners":2,"numberOfActiveRunners":2,"lastMatchTime":"2015-03-06T12:11:27.884Z",
    "totalMatched":1966461.12,
    "totalAvailable":839923.59,"crossMatching":true,"runnersVoidable":false,"version":927573762,
    "runners":[
    {"selectionId":3375664,"handicap":0.0,"status":"ACTIVE","lastPriceTraded":2.36,
    "totalMatched":0.0,
    "ex":{"availableToBack":[{"price":2.3,"size":296.35},{"price":2.28,"size":4399.91},{"price":2.26,"size":21.09}],"availableToLay":[{"price":2.36,"size":1215.93},{"price":2.38,"size":408.39},{"price":2.4,"size":4306.3}],"tradedVolume":[]}},
    {"selectionId":5497360,"handicap":0.0,"status":"ACTIVE","lastPriceTraded":1.74,
    "totalMatched":0.0,
    "ex":{"availableToBack":[{"price":1.74,"size":1457.78},{"price":1.73,"size":754.35},{"price":1.72,"size":6008.8}],"availableToLay":[{"price":1.76,"size":387.28},{"price":1.77,"size":5149.84},{"price":1.78,"size":514.93}],"tradedVolume":[]}}]}
    ],"id":1}]
    Do you have any idei why it is not work?
    It works for other matches and worked for this match hour ago, but not now.

    Thanks in advance!
  • komposter
    Junior Member
    • Mar 2015
    • 17

    #2
    Investigation

    My investigation revealed that this problem started approximately at 12:00 (GMT+2).
    Ivalid totalMatched returns for many matches, including following market IDs:
    1.117618413
    1.117621723
    1.117623384
    1.117621987
    1.117592185
    1.117619925
    1.117620058

    Comment

    • betdynamics
      Junior Member
      • Sep 2010
      • 534

      #3
      Make sure you are using your "live" appkey and not your "delayed" appkey as totalMatched is only returned for the live version.

      Comment

      • komposter
        Junior Member
        • Mar 2015
        • 17

        #4
        Originally posted by betdynamics View Post
        Make sure you are using your "live" appkey and not your "delayed" appkey as totalMatched is only returned for the live version.
        Thanks for you reply.
        I'm sure I use "live" key.

        As I said, my application worked continuesly, the problem appeared only at 12:00. So, before 12:00 it worked correctly, and after 12:00 it broke.

        Look at this example:


        Time LastPrice1 TotalMatched1 LastPrice2 TotalMatched2
        18:27:27 2.10 99.44 0.00 0.00
        18:34:09 2.10 99.72 1.89 17.54
        19:00:10 2.10 99.66 1.89 17.53
        19:00:49 2.10 99.69 1.89 17.53
        20:00:10 2.10 99.71 1.89 17.53
        20:07:42 2.10 99.70 1.89 17.53
        21:00:11 2.10 99.71 1.89 17.54
        21:15:32 2.08 325.79 1.92 27.29
        22:00:11 2.08 325.99 1.92 27.31
        22:07:11 2.08 325.90 1.92 27.30
        23:00:11 2.08 325.73 1.92 27.29
        23:01:41 2.08 325.81 1.92 27.30
        00:00:11 2.08 326.00 1.92 27.31
        00:13:31 2.08 325.91 1.92 27.30
        00:16:31 1.88 331.53 1.92 27.30
        01:00:12 1.88 331.79 1.92 27.33
        01:00:52 1.88 331.67 1.92 27.31
        01:16:22 1.91 339.45 1.92 27.31
        01:23:43 1.91 343.19 1.97 43.74
        02:00:12 1.91 343.07 1.97 43.72
        02:02:42 1.91 343.13 1.97 43.74
        02:44:12 1.94 373.14 1.97 43.74
        03:00:12 1.94 372.89 1.97 43.71
        03:06:43 1.94 372.99 1.97 43.70
        04:00:09 1.94 373.11 1.97 43.72
        04:00:38 1.94 373.07 1.97 43.72
        05:00:12 1.94 373.09 1.97 43.72
        05:01:12 1.94 373.08 1.97 43.71
        05:04:12 1.94 373.08 2.08 78.31
        05:52:01 1.94 412.00 2.06 114.90
        06:00:12 1.94 412.16 2.06 114.94
        06:13:42 1.94 412.09 2.06 114.95
        07:13:42 1.94 412.09 2.06 114.94
        07:32:42 1.93 426.09 2.06 114.94
        07:42:12 1.94 482.79 2.06 114.94
        07:46:22 1.94 494.79 2.06 114.94
        07:59:32 1.95 565.01 2.04 182.06
        07:59:42 1.95 566.58 2.04 182.06
        08:00:12 1.95 566.43 2.04 182.01
        08:09:12 1.95 591.29 2.04 181.99
        08:09:22 1.94 606.49 2.04 181.99
        08:10:12 1.99 610.39 1.99 185.91
        08:16:02 1.95 621.41 1.99 185.91
        08:16:42 1.94 800.38 1.99 185.91
        08:28:12 1.96 805.90 2.04 191.20
        08:35:12 1.98 821.33 2.02 206.32
        08:38:32 1.98 836.33 2.02 221.03
        08:48:52 1.98 844.32 2.02 221.03
        08:58:02 2.00 855.35 2.00 232.05
        09:00:12 2.00 855.07 2.00 231.98
        09:02:22 2.00 855.15 2.00 231.94
        09:20:41 2.00 855.15 2.00 262.18
        09:55:14 2.00 866.17 2.00 273.19
        10:00:04 2.00 865.94 2.00 273.12
        10:12:34 2.00 866.24 2.00 273.26
        10:24:23 2.00 869.55 2.00 276.57
        10:33:34 2.00 874.12 2.00 281.15
        10:37:14 2.00 880.62 2.00 287.65
        10:41:14 1.99 888.62 2.00 287.65
        11:00:04 1.99 887.40 2.00 287.25
        11:00:54 1.99 888.24 2.00 287.40
        11:01:54 1.98 1926.93 2.00 287.40
        11:03:03 1.96 1931.63 2.04 291.80
        11:14:07 1.89 1949.14 2.12 293.84
        11:54:15 1.90 2015.16 2.12 293.84
        12:00:05 1.90 2013.31 2.12 293.57
        12:00:25 1.98 2041.32 2.02 320.91
        12:00:35 1.98 2040.27 2.02 320.78
        12:00:45 2.00 2112.07 2.00 392.41
        12:03:35 2.00 0.00 2.00 0.00
        12:03:44 2.00 2112.07 2.00 392.41
        12:03:54 2.00 0.00 2.00 0.00
        12:04:04 2.00 2112.07 2.00 392.41
        12:04:24 1.91 2192.13 2.00 392.41
        12:04:34 2.00 0.00 2.00 0.00
        12:04:45 1.91 2192.13 2.00 392.41
        12:05:15 1.91 0.00 2.00 0.00
        12:05:25 1.90 0.00 2.00 0.00
        12:05:35 1.90 2212.14 2.00 392.41
        12:05:54 1.90 0.00 2.00 0.00
        12:06:05 1.90 2212.14 2.00 392.41
        12:06:45 1.90 0.00 2.00 0.00
        12:07:05 1.89 2505.04 2.12 394.26
        12:07:25 1.90 0.00 2.00 0.00
        12:07:35 1.89 0.00 2.12 0.00
        12:08:05 1.89 2505.04 2.12 394.26
        12:08:15 1.89 0.00 2.12 0.00
        12:08:35 1.89 2505.04 2.12 394.26
        12:08:45 1.89 0.00 2.12 0.00
        12:10:05 1.89 2505.04 2.12 394.26
        12:10:15 1.89 0.00 2.12 0.00
        12:12:14 1.88 0.00 2.12 0.00
        12:12:34 1.89 0.00 2.12 0.00
        12:12:54 1.88 0.00 2.12 0.00
        12:14:03 1.88 0.00 1.99 0.00
        12:27:25 1.87 0.00 1.99 0.00
        12:40:23 1.90 0.00 1.99 0.00
        12:40:33 1.87 0.00 1.99 0.00
        12:41:03 1.90 0.00 1.99 0.00
        12:41:33 1.91 0.00 1.99 0.00
        12:50:15 1.91 0.00 2.12 0.00
        12:50:25 1.91 0.00 1.99 0.00
        12:50:40 1.91 0.00 2.12 0.00
        12:53:20 1.88 0.00 2.12 0.00
        12:53:40 1.91 0.00 2.12 0.00


        I have many tables like this. LastMatched price works correctly, but totalMatched doesn't.

        Thanks for your help!

        Comment

        • betdynamics
          Junior Member
          • Sep 2010
          • 534

          #5
          The JSON that you posted in your original message seemed to indicate that the market data was delayed (isMarketDataDelayed = true), hence my point about live and delayed appkeys.

          Do you have the JSON reponses for times when a totalMatched is returned? If so, can you compare a working response and a non-working response?

          You then need to send all the relevant details to the BDP team (bdp@betfair.com) so they can investigate.

          From memory, there was a similar problem reported a few months back.
          Last edited by betdynamics; 06-03-2015, 11:35 PM.

          Comment

          • komposter
            Junior Member
            • Mar 2015
            • 17

            #6
            I think you're right.

            Earlier I received the not delayed data.

            Now I have "delayed" flag on both app-keys:


            I'll contact betfair team to resolve this problem.
            Thank you for your help!

            Comment

            • komposter
              Junior Member
              • Mar 2015
              • 17

              #7
              The problem has resolved.

              My fault was I used live-key while developing (without any bets) and BF blocked my live-key. After I changed it to delayed key and promised not to use live-key before live-testing (with real bets), they activated it again.

              Thanks for help!

              Comment

              Working...
              X