Stream API Delayed not including SUB_IMAGE in MC response

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • TheTrainer
    Junior Member
    • Mar 2019
    • 2

    #1

    Stream API Delayed not including SUB_IMAGE in MC response

    Hi, I am quite new to working with the Betfair suite of APIs. I have got the majority of it all working, however I am now working with the Stream API.

    I am building this in Node.js, using the delayed API Key and request to 'stream-api-integration.betfair.com' to horse racing markets.

    I am subscribing successfully to both Market and Order streams and getting an initial oc and mc responses, with SUB_IMAGE provided.

    However, after the delay of 300 seconds or whatever for delayed streams, I then receive the following mcm op that does not include a SUB_IMAGE parameter, even though the response is split into multiple messages to the client:

    {"op":"mcm","id":2,"clk":"AO6VAgD2tQEAgZ4B","pt ":1 574446287032,"mc":[{"id":"1.165374963","rc":[{"atb":[[9.......to much data to paste here...

    So, what am I not understanding here, if the request is sent in multiple parts, but does not tell me that it is?

    I have another issue relating to when the the market turns in play, the 'inplay' attribute always stays as false, and I also sometimes receive market closed long before the market has even gone in play. I assume I am just not understanding the documentation very well. Any help appreciated, thanks.
  • WTPooh
    Member
    • May 2012
    • 88

    #2
    • ct= ChangeType - this enumeration is used to identify the type of change
      • SUB_IMAGE - The initial image returned from a subscribe
      • RESUB_DELTA - A patch returned from a resubscribe
      • HEARTBEAT - An empty message published if no data has been sent within heartbeatMs
        • We send these to maintain the connection to you and detect closed connections
        • You can use the heartbeatMs to verify that you are still connected
      • <null / not set> - An update message
    • segmentType - SegmentType - this enumeration identifies multi-part segmented messages:
      • SEG_START - Start of a segmented message
      • SEG - Middle part of a segmented message
      • SEG_END - Last part of a segmented message
      • <null / not set> - A non-segmented message


    Comment

    • TheTrainer
      Junior Member
      • Mar 2019
      • 2

      #3
      lol right I didn't read it very clearly then. I have solved the other issues as well.
      Thanks WTPooh!

      Comment

      Working...
      X