how do you get ric details in api
I can get a Ric of a future or option using Search/HistoricalChainResolution or /Search/FuturesAndOptionsSearch the results have some details like Key, Identifier, Description etc and of course the Ric
If I copy the Ric into the search field in web ui I can get more info, like expiration date.
How do I get that from that API. I tried using Search/ReferenceHistory but got nothing back. For example this body returns nothing:
{ "Request": { "Rics": [ "ESH0^0" ], "Range": { "Start": "1990-01-01T00:00:00.000Z", "End": "2017-05-15T00:00:00.000Z" } } }
Best Answer
-
Hi @dorlovsky,
The answer provided by the content team:
"Clients were directed to use T&Cs as a
temporary workaround when Historical Reference template was being built.
However, T&Cs merely hold live reference data. It does not hold Historical
Reference data. Clients looking for references on Futures and Options (which
typically expires every month) and other instruments that expire will get
reference data only via. Historical Reference template. For the sake of
simplicity, Tick History clients must use the Historical Reference template for
reference data on all asset categories (minus fixed income references).
"For an example, please refer to the following request:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Currency Code", "Expiration Date", "Lot Size"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "ESH0^0",
"IdentifierType": "Ric"
}]
},
"Condition": {
"StartDate": "2007-09-29T00:00:00.000Z",
"EndDate": "2017-09-29T12:00:00.000Z"
}
}
}0
Answers
-
I found that the expiration date of ESH0^0 is available via TermsAndConditionsExtractionRequest.
Then, I used on Demand Extraction with this URL to send the request.
POST: https://hosted.datascopeapi.reuters.com/RestApi/V1/Extractions/Extract
The request message is:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Currency Code", "Expiration Date", "Lot Size"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "ESH0^0",
"IdentifierType": "Ric"
}
]
}
}
}The response is:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionRow)",
"value": [
{
"IdentifierType": "Ric",
"Identifier": "ESH0^0",
"RIC": "ESH0^0",
"CUSIP": null,
"ISIN": null,
"SEDOL": null,
"Issuer OrgID": null,
"Currency Code": "USD",
"Expiration Date": "2000-03-17",
"Lot Size": 50
}
]
}For more information, please refer to:
0 -
this is not at all obvious! how did you know to do that? how would I?
What url are you invoking this on?
The api doc does not show you can show you can do any kind of body at all!
https://hosted.datascopeapi.reuters.com/RestApi.Help/Context/Entity?ctx=Extractions&ent=TermsAndConditionsReportTemplate&sce=Report Template Examples - Create - Terms and Conditions&stp=1&tab=20 -
I used on Demand Extraction with this URL.
POST: https://hosted.datascopeapi.reuters.com/RestApi/V1/Extractions/Extract.
First, I verified the list of available fields for Term & Conditions and found the "Expiration Date" and "Lot Size" fields in the list.
For more information, please refer to:
0 -
@dorlovsky
You can also find all available fields for report templates in the "Field Descriptions" tab of the TICK HISTORY DATA DICTIONARY document. The document can be downloaded from this link.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 622 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 676 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛