PriceHistoryExtractionRequest vs TimeSeriesExtractionRequest

vikas.khurana
vikas.khurana Explorer
in DSS

It seems from the documentation that I should use the PriceHistoryExtractionRequest over the TimeSeriesExtractionRequest but I don't see any examples for it. Is that the case? Are there any significant differences I should be aware of?

Tagged:

Best Answer

  • Ramprasad.Kumaralu.J
    Ramprasad.Kumaralu.J LSEG
    Answer ✓ 
    POST https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes HTTP/1.1 Authorization: Token <your_auth_token_goes_here> Prefer: respond-async Content-Type: application/json; odata=minimalmetadata { "ExtractionRequest": { "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest", "ContentFieldNames": [ "Ask High", "Ask Low", "Bid High", "Bid Low", "Trade Date" ], "IdentifierList": { "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList", "InstrumentIdentifiers": [ { "Identifier": "TRI.N", "IdentifierType": "Ric" } ], "ValidationOptions": null, "UseUserPreferencesForValidationOptions": false }, "Condition": { "QueryStartDate": "2015-12-01T00:00:00.000Z", "QueryEndDate": "2015-12-02T00:00:00.000Z" } } } 

    Response

     HTTP/1.1 200 OK 

    @{ "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.ExtractionResult", "Contents": [ { "IdentifierType": "Ric", "Identifier": "TRI.N", "Ask High": null, "Ask Low": null, "Bid High": null, "Bid Low": null, "Trade Date": "2015-12-01" }, { "IdentifierType": "Ric", "Identifier": "TRI.N", "Ask High": null, "Ask Low": null, "Bid High": null, "Bid Low": null, "Trade Date": "2015-12-02" } ], "Notes": [ "Extraction Services Version 12.0.38496 (4b10cc09ac17), Built Mar 9 2018 22:12:54\r\n Processing started at 03/12/2018 PM 08:17:56.\r\n User ID: 20058\r\n Extraction ID: 2000000001130828\r\n Schedule: 0x0618fef979084050 (ID = 0x0000000000000000)\r\n Input List (1 items): (ID = 0x0618fef979084050) Created: 03/12/2018 PM 08:17:56 Last Modified: 03/12/2018 PM 08:17:56\r\n Report Template (11 fields): _OnD_0x0618fef979084050 (ID = 0x0618fef99b684050) Created: 03/12/2018 PM 08:17:52 Last Modified: 03/12/2018 PM 08:17:52\r\n Schedule dispatched via message queue (0x0618fef979084050)\r\n Schedule Time: 03/12/2018 PM 08:17:54\r\n Timeseries Date Range: 12/01/2015 to 12/02/2015\r\n Processing completed successfully at 03/12/2018 PM 08:18:07, taking 10.871 Secs.\r\n Extraction finished at 03/12/2018 PM 08:18:07 UTC, with servers: x04q11, ETS (10.4 secs), QSDEV1 (0.0 secs), QSSDB2 (0.0 secs)\r\n Usage Summary for User 20058, Client 11286, Template Type Price History\r\n \r\n Base Usage\r\n Instrument Instrument Terms Price\r\n Count Type Subtype Source Source\r\n ------- ----------------------------------- ---------------------------- -------------- ----------------------------------------\r\n 1 Equities N/A N/A\r\n -------\r\n 1 Total instrument charged.\r\n 0 Instruments with no reported data.\r\n =======\r\n 1 Instrument in the input list.\r\n No TRPS complex usage to report -- 1 Instrument in the input list had no reported data.\r\n Writing RIC maintenance report.\r\n" ] }

    @vikas.khurana, yes, please use PriceHistroryExtracion request over TimeseriesExtractionRequest because price history has more data points than TimeseriesTemplate. Also eventually, timeseries will become legacy An example is available in API Reference Tree-->Extractions-->on Demand Extractions--> ExtractionWithNotes

Categories