Hi @adam_strakna,

When making requests for data, the default behavior is to "Stream" the data, meaning, you get back an initial ('refresh') image and then when market conditions change, you will receive streaming updates. In your case, you will want to override the default behavior and request for "NonStreaming" data. Doing this, you will only receiving the initial image. So, your request will look something like this:

{
  "ID": 2,
  "Streaming": false,
  "Key": {
    "Name": [
      "TRI.N",
      "IBM.N",
      "JUNK.X"
    ]
  }
}

The attribute "Streaming" will control streaming vs non-streaming. The default is true - stream. In your case, you will set it to false - as above. When you make a non-streaming request, once you get a response back for an item, that stream will be automatically closed. You do not need to explicitly close the stream.

In the example above, I've requested for a batch of 3 items, 2 valid ones and one invalid. I did this intentionally to show you the proper way to detect when ALL requests have been fulfilled so you can determine that your request/response has completed.

The "ID" field within the request will drive this. When making a batch request, the server will automatically assign the next 3 subsequent ID's to each of the items within your batch. So in the above example, ID 3 will be assigned to 'TRI.N', ID 4 to 'IBM.N' and ID 5 to 'JUNK.X'.

When you make your request, you will get back the refresh for each of the valid items, i.e. ID 3 and ID 4. For example:

[
  {
    "ID": 3,
    "Type": "Refresh",
    "Key": {
      "Service": "IDN_SELECTFEED",
      "Name": "TRI.N"
    },
    "State": {
      "Stream": "NonStreaming",
      "Data": "Ok",
      "Text": "All is well"
    },
   ...

For the invalid symbol, 'JUNK.X' you will get back a Status message:

  {
    "ID": 5,
    "Type": "Status",
    "Key": {
      "Service": "IDN_SELECTFEED",
      "Name": "JUNK.X"
    },
    "State": {
      "Stream": "Closed",
      "Data": "Suspect",
      "Code": "NotFound",
      "Text": "The record could not be found"
    }

Your application will simply need to monitor all 'Refresh' and 'Status' messages for the ID's you are expecting back. Once all have arrived, the batch request has been fulfilled.

Hope this helps.