Hi,
Could someone create a basic JSON example using the "Symbol Cross Reference" Template, where the CUSIP or SEDOL is used as input to get the corresponding ISIN.
Thanks,
Greg
For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
Hi,
Could someone create a basic JSON example using the "Symbol Cross Reference" Template, where the CUSIP or SEDOL is used as input to get the corresponding ISIN.
Thanks,
Greg
Hello @Gregor,
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
-AHS
@Gregor,
Here is a simple On Demand example (easier than to define a template and run a schedule):
POST https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
Body of the request:
{ "ExtractionRequest": { "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.SymbolCrossReferenceExtractionRequest", "ContentFieldNames": [ "Alternate Identifier", "Alternate Identifier Type", "Reuters Editorial RIC" ], "IdentifierList": { "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList", "InstrumentIdentifiers": [ { "Identifier": "2005973", "IdentifierType": "Sedol" }, { "Identifier": "00209tab1", "IdentifierType": "Cusip" } ], "ValidationOptions": { "AllowOpenAccessInstruments": true, "AllowHistoricalInstruments": true, "AllowInactiveInstruments": true }, "UseUserPreferencesForValidationOptions": false }, "Condition": { "IdentifierTypes": [ "Isin" ] } } }
Response:
{ "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult", "Contents": [ { "IdentifierType": "Sedol", "Identifier": "2005973", "Alternate Identifier": "US4592001014", "Alternate Identifier Type": "ISN", "Reuters Editorial RIC": "IBM.N" }, { "IdentifierType": "Cusip", "Identifier": "00209TAB1", "Alternate Identifier": "US00209TAB17", "Alternate Identifier Type": "ISN", "Reuters Editorial RIC": null } ], "Notes": [ "Extraction Services Version 13.2.41212 (c22dc546d81e), Built Nov 18 2019 19:25:40\r\nUser has overridden estimates broker entitlements.\r\nProcessing started at 10122019 18:02:26.\r\nUser ID: 33314\r\nExtraction ID: 2000000117327960\r\nSchedule: 0x06e620a9cd1135d4 (ID = 0x0000000000000000)\r\nInput List (2 items): (ID = 0x06e620a9cd1135d4) Created: 10122019 18:02:26 Last Modified: 10122019 18:02:26\r\nReport Template (9 fields): _OnD_0x06e620a9cd1135d4 (ID = 0x06e620a9cd6135d4) Created: 10122019 18:02:24 Last Modified: 10122019 18:02:24\r\nSchedule dispatched via message queue (0x06e620a9cd1135d4)\r\nSchedule Time: 10122019 18:02:25\r\nProcessing completed successfully at 10122019 18:02:27, taking 0.182 Secs.\r\nExtraction finished at 10122019 17:02:27 UTC, with servers: x02q12, QSHC19 (0.1 secs), QSSHA1 (0.0 secs)\r\nUsage Summary for User 33314, Client 11122, Template Type Symbol Cross Reference\r\nBase Usage\r\n Instrument Instrument Terms Price\r\n Count Type Subtype Source Source\r\n------- ----------------------------------- ---------------------------- -------------- ----------------------------------------\r\n 1 Corporate Investment Grade N/A N/A\r\n 1 Equities N/A N/A\r\n-------\r\n 2 Total instruments charged.\r\n 0 Instruments with no reported data.\r\n=======\r\n 2 Instruments in the input list.\r\nWriting RIC maintenance report.\r\n", "Identifier,IdentType,Source,RIC,RecordDate,MaintType,OldValue,NewValue,Factor,FactorType\r\n" ] }
Hope this helps.