Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TRTH /
avatar image
REFINITIV
Question by Frederic.Li · Feb 20, 2020 at 10:15 AM · tick-history-rest-apichain-ric

No start and end time in the response of HistoricalChainResolution?

Good day experts,

I'm trying the 'get historical chain' operation, the request body is:

{
"Request": {
"ChainRics": [
"0#.SPX"
],
"Range": {
"Start": "2008-01-01T00:00:00.000Z",
"End": "2008-01-01T00:00:00.000Z"
}
}
}


And the response looks like:

...

"Constituents": [
{
"Identifier": ".SPX",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwuU1BYfA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6"
},
{

...


It missed the 'Start' and 'End' time fields?

e.g., in the ' TICK HISTORY FOR DATASCOPE SELECT 13.2 REST API USER GUIDE''s example:

...

"Constituents": [
{
"Identifier": "HOF0",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT0Ywf
A",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"Start": "2008-01-01T00:00:00.000Z",
"End": "2008-01-01T00:00:00.000Z"
},
{

...


Is that true or I miss some settings in the http request?


Best Regards,

Frederic

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.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by veerapath.rungruengrayubkul · Feb 21, 2020 at 04:16 AM

Hi @Frederic.Li,

I have verified the returned value of HistoricalChainResolution in the API Reference Tree and Metadata. There is no Start and End time field in response, so it likely is that the example result in the REST API User Guide document is not correct. To get the Valid Start and End time, you can pass the Constituents to HistoricalBulkSearch

I will contact TRTH support to verify the issue.

Comment
Frederic.Li

People who like this

1 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
REFINITIV
Frederic.Li · Feb 21, 2020 at 12:01 PM 0
Share

Thank you Veerapath, looks like the HistoricalBulkSearch does not touch/display the history chain itself and when a constituent was added into that chain.

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 >
9 People are following this question.

Related Questions

Working R examples for Eikon with Lipper data

grab chainric data through rest api

I need to resolve a chain of historical RICS, e.g. 0#TFI: how do I qualify historical RIC chains in the API?

VIX futures, how to get the contracts chain list of the VIX?

How to retrieve more informations (assetName, PermID, ISIN, ecc...) about constituents retrieved by a HistoricalChainResolution request?

  • 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