Tick History (DS) REST API - Original Input Identifier Not Included in Output Response?
Hi,
I'm interested in advising client to use the Bulk Historical Search to get RICs from a list of identifiers , in this case resolving from using ISIN (input) to RIC (output).
The below appears to be what I am looking for, however the result do not include the original identifier being used so I am unable to determine which ISIN each RIC in the was resolved from:
POST https://selectapi.datascope.refinitiv.com/restapi/v1/Search/HistoricalBulkSearch
Authorization: Token {{Token}}
Prefer: respond-async
Content-Type: application/json; odata=minimalmetadata
{
"Request": {
"Identifiers": [
{
"Identifier": "CND1000291L3",
"IdentifierType": "Isin"
},
{
"Identifier": "CND1000014N5",
"IdentifierType": "Isin"
}
],
"Range": {
"Start": "1996-01-01T00:00:00.000Z",
"End": "2021-09-17T00:00:00.000Z"
}
}
}
Example truncated output, I was expecting the original identifier to form part of the collection:
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/restapi/v1/$metadata#DataScope.Select.Api.Search.HistoricalBulkSearchResult",
"Results": [
{
"Identifier": "190006=CCTB",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwxOTAwMDY9Q0NUQnw",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2020-04-30T00:00:00.000Z",
"LastDate": "2021-09-11T00:00:00.000Z",
"History": []
},
{
"Identifier": "190006=CCTZ",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwxOTAwMDY9Q0NUWnw",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2021-05-27T00:00:00.000Z",
"LastDate": "2021-09-11T00:00:00.000Z",
"History": []
},
{
"Identifier": "CN019616=ESS",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxDTjAxOTYxNj1FU1N8",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2019-06-03T00:00:00.000Z",
"LastDate": "2021-09-17T00:00:00.000Z",
"History": []
},
...
Is the original identifier something that could be added to the response collection?
Best regards,
Gareth
Best Answer
-
Hello @gteage ,
Depending on the use case requirements, and if RDP permissioining is available, you may wish to proceed via RDP Search Beta, a very simple usage, for example:
https://{{RDP_HOST}}/discovery/search/v1/
{
"View": "Instruments",
"Filter": "ISIN in ( 'CND1000291L3' 'CND1000014N5')",
"Select": "ISIN, RIC"
}Resulting in:
{
"Total": 2,
"Hits": [
{
"ISIN": "CND1000291L3",
"RIC": "CN190006="
},
{
"ISIN": "CND1000014N5",
"RIC": "CN080020="
}
]
}Or RDP Symbology, for example:
https://{{RDP_HOST}}/discovery/symbology/{{RDP_VERSION_SYMBOLOGY}}/lookup
{
"from": [
{
"identifierTypes": ["Isin"],
"values": ["CND1000291L3","CND1000014N5"]
}
],
"type": "auto",
"to": [
{
"identifierTypes": ["RIC"]
}
]
}Resulting in:
{
"data": [
{
"input": [
{
"value": "CND1000014N5",
"identifierType": "Isin"
}
],
"output": [
{
"value": "CN080020=CFIC",
"identifierType": "RIC"
},
{
"value": "CN080020=CNMB",
"identifierType": "RIC"
},
{
"value": "CN100820=SZ1",
"identifierType": "RIC"
},
{
"value": "CN080020=SYSJ",
"identifierType": "RIC"
},
{
"value": "CN080020=RRPS",
"identifierType": "RIC"
},
...
{
"input": [
{
"value": "CND1000291L3",
"identifierType": "Isin"
}
],
"output": [
{
"value": "CN190006=SYSJ",
"identifierType": "RIC"
},
{
"value": "CN190006=RRPS",
"identifierType": "RIC"
},
{
"value": "CN190006=IBCN",
"identifierType": "RIC"
},
...0
Answers
-
Hello @gteage ,
Would it work for your use case to proceed this way:
https://selectapi.datascope.refinitiv.com/restapi/v1/Search/HistoricalBulkSearch
{
"Request": {
"Identifiers": [
{
"Identifier": "CND1000291L3",
"IdentifierType": "Isin",
"UserDefinedIdentifier": "CND1000291L3"
},
{
"Identifier": "CND1000014N5",
"IdentifierType": "Isin",
"UserDefinedIdentifier": "CND1000014N5"
}
],
"Range": {
"Start": "1996-01-01T00:00:00.000Z",
"End": "2021-09-17T00:00:00.000Z"
}
}
}Resulting in:
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#DataScope.Select.Api.Search.HistoricalBulkSearchResult",
"Results": [
{
"Identifier": "190006=CCTB",
"IdentifierType": "Ric",
"UserDefinedIdentifier": "CND1000291L3",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwxOTAwMDY9Q0NUQnw",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2020-04-30T00:00:00.000Z",
"LastDate": "2021-09-11T00:00:00.000Z",
"History": []
},
...0 -
@zoya faberov Thanks Zoya, I think the RDP Symbology API option works well as it appears to be syncronous only.
Many thanks,
Gareth
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 中文论坛