GUI successfully extracts data using OCC, can't seem to get the equivalent to work in API
Hi,
After my API call to DSS failed to recognise my Identifier: SINA150612C00057000, with Identifier Type: OCCCode ('Not Found') I tried the extraction using GUI for the same Identifier and I am not sure what I am doing wrong by the GUI extraction worked fine, just want to replicate the same success via API On Demand, my unsuccessful extraction below:
POST .../Extractions/ExtractWithNotes
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"Asset Category",
"Trading Symbol",
"OCC Code",
"RIC"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "SINA150612C00057000",
"IdentifierType": "OCCCode"
}
],
"ValidationOptions": {
"AllowHistoricalInstruments": false,
"AllowInactiveInstruments": false,
"AllowLimitedTermInstruments": false,
"AllowOpenAccessInstruments": false,
"AllowSubclassImport": false,
"AllowUnsupportedInstruments": true,
"ExcludeFinrAsPricingSourceForBonds": false,
"UseConsolidatedQuoteSourceForCanada": false,
"UseConsolidatedQuoteSourceForUsa": false,
"UseDebtOverEquity": false,
"UseExchangeCodeInsteadOfLipper": true,
"UseOtcPqSource": true,
"UseUsQuoteInsteadOfCanadian": true
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": null
}
}
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult",
"Contents": [
{
"IdentifierType": "OCCCode",
"Identifier": "SINA150612C00057000",
"Error": "Not found"
}
],
"Notes": [
"All identifiers were invalid. No extraction performed."
]
}
Best Answer
-
I assume that when using GUI, you have used Futures & Options Search to search for SINA150612C00057000 (OCCCode). The search result is a RIC that is added to the instrument list.
You can do the same in the API.
1. Use Search/FuturesAndOptionsSearch to search for SINA150612C00057000 (OCCCode)
{
"SearchRequest": {
"FileCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"IdentifierType": "OCCCode",
"Identifier": "SINA150612C00057000",
"PreferredIdentifierType": "Ric"
}
}2. The output is:
"value": [
{
"Identifier": "SINAF121505700.U",
"IdentifierType": "Ric",
"Source": "OPQ",
...
"Description": "SINA 2Jn5 57.0 C",
"InstrumentType": "Derivative",
"Status": "Valid",
"ExchangeCode": "OPQ",
"CurrencyCode": "USD",
"FuturesAndOptionsType": "Options",
"PutCallCode": "Call",
"ExpirationDate": "2015-06-12T00:00:00.000Z",
"StrikePrice": 57,
"AssetStatus": "Active"
}
]3. Then use the returned RIC (SINAF121505700.U) in the extraction
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"Asset Category",
"Trading Symbol",
"OCC Code",
"RIC"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "SINAF121505700.U",
"IdentifierType": "Ric"
}
],
"ValidationOptions": {
"AllowHistoricalInstruments": false,
"AllowInactiveInstruments": false,
"AllowLimitedTermInstruments": false,
"AllowOpenAccessInstruments": false,
"AllowSubclassImport": false,
"AllowUnsupportedInstruments": true,
"ExcludeFinrAsPricingSourceForBonds": false,
"UseConsolidatedQuoteSourceForCanada": false,
"UseConsolidatedQuoteSourceForUsa": false,
"UseDebtOverEquity": false,
"UseExchangeCodeInsteadOfLipper": true,
"UseOtcPqSource": true,
"UseUsQuoteInsteadOfCanadian": true
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": null
}
}You may contact the DSS support team via MyRefinitiv to verify why the OCCCode doesn't work with the TermsAndConditionsExtractionRequest.
0
Answers
-
We found that you can use IdentifierType = Sym in the extract call instead of OCCCode and it works.
Sym = Trading Symbol = Exchange-supplied code used for trading purposes to uniquely identify an instrument.
"IdentifierType": "Sym"
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
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 WebSocket API
- 37 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
- 275 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
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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
- 46 中文论坛