Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • DSS /

For a deeper look into our DataScope Select REST API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials

avatar image
Question by bob1 · Jan 16, 2020 at 03:27 AM · dss-rest-apidatascope-selectdsspricingchain-ric

Futures ChainRic resolving to Cash products

I am seeing the following log message, which is giving me an error (when retrieving time and sales):

Instrument <CHR,0#SIN:> expanded to 7 RIC instances: .NSEI to SINZ9. Quota Message: INFO: Tick History Cash Quota Count Before Extraction: 0; Instruments Approved for Extraction: 0; Tick History Cash Quota Count After Extraction: 0, 100% of Limit;\  Tick History Cash Quota Limit: 0 Quota Message: ERROR: The RIC '.NSEI' in the request would exceed your quota limits. Adjust your input list to continue. Quota Message: WARNING: Tick History Cash Quota has been reached or exceeded

I would not like to retrieve the underlying.

Is there a way to filter out the underlying when looking up products by their chain rics?

I would like to have the following chain ric expansion instead:

Instrument <CHR,0#SIN:> expanded to 6 RIC instances: SINH0 to SINZ9.

This is how it resolves for me when I'm retrieving it with market depth.

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

3 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by veerapath.rungruengrayubkul · Jan 16, 2020 at 07:46 AM

The <NBBZ9> is historical RIC as it is valid until 14/12/2019.

To extract data for historical RIC, you need to add "AllowHistoricalInstruments": true of the ValidationOptions and "UseUserPreferencesForValidationOptions": false in extraction request. We recommend using the normal RIC instead of the delisted RIC (i.e. NBBZ9^1).

Below is the sample of request.

{ 
    "ExtractionRequest": 
    { "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryTimeAndSalesExtractionRequest", 
     "ContentFieldNames":
     [     
         ...
        ], 
     "IdentifierList": {"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
     "InstrumentIdentifiers": [
            {"Identifier": "NBBZ9",
            "IdentifierType": "Ric"
            }
     ],
        "ValidationOptions": {
            "AllowHistoricalInstruments": true
        },
        "UseUserPreferencesForValidationOptions": false
    },"Condition":



1579160842036.png (32.8 KiB)
Comment
bob1

People who like this

1 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
REFINITIV
Answer by veerapath.rungruengrayubkul · Jan 16, 2020 at 06:59 AM

Hi @bob1,

There is no interface to filter underlying RICs for Chain expansion. You may get all underlying using Historical Chain Constituents Search to manually filter the Cash underlying first, and then extract data with the filtered underlying.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
Answer by bob1 · Jan 16, 2020 at 07:19 AM

I have tried using historical chains for expanding my chain rics, but it does not work.

For example, if I expand the chainric "0#NBB:" from 2019-11-01 - 2019-01-01, then I get the following rics:

"NBBH0", "NBBH1", "NBBH2", "NBBM0", "NBBM1", "NBBM2", "NBBU0", "NBBU1", "NBBU2", "NBBZ0", "NBBZ1", "NBBZ2", "NBBZ9".

This is not valid to look up particular rics. For example, "NBBZ9" is now called "NBBZ9^1". If I used "NBBZ9" to search up data from 2019-11-01 - 2019-01-01, I would fetch no data. If i used "NBBZ9^1" then I can fetch the data. However, there is no way for me to know that it's "NBBZ9^1" that I want to choose.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

avatar image
nathan.faber · Jul 16, 2021 at 02:05 PM 0
Share
Hi @bob1 Did you ever get this resolved? I am running into very similar issues. Thanks!

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
12 People are following this question.

Related Questions

it happened many times this month that the end of day prices for all equities in the U.S. Market are not extracted

Querying for market volume

Universal Close Price not coming for non traded equities from API

DataScope: Where can I find those chain rics?

Intra day pricing Timeouts

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges