question

Upvotes
Accepted
588 8 13 16

RIC Expansion differences between TRTH Web and DataServices API

I am comparing the following two chains while using TRTH Web (Version 6.0.11:Data 72) and the TRTH Data Services API. For the 12/01/2014 00:00 through 12/31/2014 23:59:59.999 date/time range:
  • 0#USAFLRRPS1 expands to 8 instruments via TRTH web but 10 instruments via TRTH Data Services
  • 0#USRPBB-ADT1 expands to 10 instruments via TRTH web but 12 instruments via TRTH Data Services
Why is there a discrepancy between the two sources?
tick-history-rest-apidelivery
icon clock
10 |1500

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

1 Answer

Upvotes
Accepted
322 5 12 16

RRPSHRD1(FID800) and RRPSBONDS(FID 801) from the chains 0#USAFLRRPS1 and 0#USRPBB-ADT1 unfortunately cannot be removed as they are required to be on the chain for the convenience of desktop users.

From the above desktop snapshot, if you observe RRPSBONDS in 801, it helps desktop users to navigate back to the parent speed guide page. And RRPSHRD1 strings all the labels such as Issue, Coupon, Maturity etc together. In absence of FID 801 these labels will not be seen. There's a purpose for their existence and it can't be removed. RRPSHRD1(FID800) and RRPSBONDS(FID 801) are pages and not RICS. Now GUI shows them as invalid as GUI verifies the chain and only updates its corresponding RICS on the instrument list page. The API on the other hand (unlike GUI which has a dedicated speedguide page option) also includes the SpeedGuide page in its expansion. This is the reason as to why you view the above RICS Thus my suggestion would be for you to ignore these instruments while requesting for data.

icon clock
10 |1500

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

Click below to post an Idea Post Idea