question

Upvotes
Accepted
50 10 14 27

VBD data availability issue

Exchange File type

EUX CORP

EUX REF

EUX Instruments

CBT CORP

CBT REF

CBT Instruments

The above mentioned files types are not availble for the date 07-08-2017. We tried to get the entire list of files for the exchanges CBT and EUX. Also there is no link at the end of the list using which we could get next set of files. We use below queries for the same.

EUX:

curl -k -X GET -H "Content-Type: application/json" -H "Prefer: respond-async" -H "Accept-Charset: UTF-8" -H "Authorization: Token xxxxxxxxxxx" https://10.192.6.221/RestApi/v1/StandardExtractions/UserPackageDeliveryGetUserPackageDeliveriesByPackageId%28PackageId%3D%270x04f21a8d1c059cb1%27%29

CBT:

curl -k -X GET -H "Content-Type: application/json" -H "Prefer: respond-async" -H "Accept-Charset: UTF-8" -H "Authorization: Token xxxxxxxxxxx" https://10.192.6.221/RestApi/v1/StandardExtractions/UserPackageDeliveryGetUserPackageDeliveriesByPackageId%28PackageId%3D%270x04f21a8d18559cb1%27%29

Please let us know if we are missing anything.

tick-history-rest-apivenue-by-day
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
56.2k 145 45 65

The response contains the "@odata.nextlink" field.

...
{
      "PackageDeliveryId": "0x05d3d45a02bb3026",
      "UserPackageId": "0x04f21a8d1c059cb1",
      "SubscriptionId": "0x0400dc1d24a00cb4",
      "Name": "EUX-2017-08-09-NORMALIZEDLL2-Data-2-of-2.csv.gz",
      "ReleaseDateTime": "2017-08-10T01:00:00.000Z",
      "FileSizeBytes": 44668593,
      "Frequency": "Daily",
      "ContentMd5": "c3dad82ab5881a73c8e6d18ae0d8de81"
    }
  ],
  "@odata.nextlink": "https:\/\/hosted.datascopeapi.reuters.com\/RestApi\/v1\/StandardExtractions\/UserPackageDeliveryGetUserPackageDeliveriesByPackageId(PackageId='0x04f21a8d1c059cb1')?$skiptoken='MjAxNy0wOC0wOVQyMjo1MjoxMS42OTAwMDAw'"
}
...

    {
      "PackageDeliveryId": "0x05d4cd8dbddb3036",
      "UserPackageId": "0x04f21a8d18559cb1",
      "SubscriptionId": "0x0400dc1d24a00cb4",
      "Name": "CBT-2017-08-12-NORMALIZEDLL2-Data-2-of-3.csv.gz",
      "ReleaseDateTime": "2017-08-13T03:00:00.000Z",
      "FileSizeBytes": 217,
      "Frequency": "Daily",
      "ContentMd5": "d077458a8e50482b8982349893877b7c"
    }
  ],
  "@odata.nextlink": "https:\/\/hosted.datascopeapi.reuters.com\/RestApi\/v1\/StandardExtractions\/UserPackageDeliveryGetUserPackageDeliveriesByPackageId(PackageId='0x04f21a8d18559cb1')?$skiptoken='MjAxNy0wOC0xMlQyMzoyNzoxOS4wMDYwMDAw'"
}

To get the next page, you need to use GET request with the URL in "@odata.nextlink" field.

However, you can change the number of entries returned in the response by specifying odata.maxpagesize in the Prefer header.

-H "Prefer: odata.maxpagesize=500; respond-async"

The default maxpagesize is 250.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

-H "Prefer: odata.maxpagesize=500; respond-async" - What max size I can specify here?

I couldn't find the limit mentioned in the document. However, it will return an error if its value exceeds 2147483646 (integer).

Moreover, it is mentioned in the Key Mechanisms that:

The page size default is 250 records for endpoints that support paging. This value can be customized although the DataScope REST API is not required to honor the requested page size. You should always code the user agent to account for the nextlink.