DSS REST API Request/Response

serhat.gulsen1
serhat.gulsen1 LSEG
in DSS

Hi,

My client is using both BBG and DSS and asking the question for DSS REST API request/response mechanism. They say that at BBG when they place a request they send a responseID which is valid for the same day. And they can use the same responseID for further data retrieval so that if it fails to return any data during the day they can try it and get over if a failure happened at the first time. They're asking if such a mechnasim exists for DSS REST API?

Thnx,

Serhat Gulsen

Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @serhat.gulsen1

    DSS REST API supports two kinds of extractions.

    1. Schedule Extraction

    With Schedule Extraction, users create instrument lists and report templates in the DSS server. Then, users set up a schedule by selecting an instrument list and a report template. The schedule can be executed one single time, or run on a recurring basis. Next, users can access the DSS Web GUI or use DSS REST API to download extracted files from the schedule.

    2. On-Demand Extraction

    With On-Demand Extraction, users send a request message that contains instrument lists and content fields to the DSS server. Then, the DSS server will process the request and return a response when the extraction is completed.

    You can refer to the DSS REST API Tutorials for more information.

Answers

  • serhat.gulsen1
    serhat.gulsen1 LSEG
    https://community.developers.refinitiv.com/discussion/comment/96659#Comment_96659

    In case of On-Demand Extraction, what if the response fails?

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @serhat.gulsen1

    If the request message is invalid, the client will get the HTTP response with the error status code, such as 400 Bad Request.

    1660800025581.png

    If it is the permission or quota issue, the client will see information from the Notes file. The Notes file contains information regarding an extraction.

    "Notes": [
            "Extraction Services Version 16.1.44123 (ed92f5e3e332), Built Aug 10 2022 01:59:14\r\nProcessing started at 08/18/2022 06:21:43.\r\nUser ID: 9008895\r\nExtraction ID: 2000000436501072\r\nCorrelation ID: CiD/9008895/AAAAAA.08221f94232e2503/RA\r\nSchedule: 0x08221f94233e2503 (ID = 0x0000000000000000)\r\nInput List (1 items):  (ID = 0x08221f94233e2503) Created: 08/18/2022 06:21:43 Last Modified: 08/18/2022 06:21:43\r\nReport Template (12 fields): _OnD_0x08221f94233e2503 (ID = 0x08221f94234e2503) Created: 08/18/2022 06:21:37 Last Modified: 08/18/2022 06:21:37\r\nSchedule dispatched via message queue (0x08221f94233e2503)\r\nSchedule Time: 08/18/2022 06:21:38\r\nNo prices needed currency scaling.\r\nReal-time data was snapped at 08/18/2022 06:21:43, it was scheduled to snap at 08/18/2022 06:21:38.\r\nProcessing completed successfully at 08/18/2022 06:21:43, taking 0.393 Secs.\r\nExtraction finished at 08/18/2022 05:21:43 UTC, with servers: x13q20, QSDHA1 (0.0 secs), QSHC15 (0.0 secs)\r\nNo embargo required for this report.\r\nUsage Summary for User 9008895, Client 65507, Template Type Intraday Pricing\r\nBase 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\nNo Evaluated Pricing Service complex usage to report -- 1 Instrument in the input list had no reported data.\r\nWriting RIC maintenance report.\r\n",
            "Identifier,IdentType,Source,RIC,RecordDate,MaintType,OldValue,NewValue,Factor,FactorType\r\n"
        ]
  • Gurpreet
    Gurpreet admin

    Hi @serhat.gulsen1,

    BBG and DSS aren't really comparable, since the data provided and delivery model is different. DSS is a REST API while former is not. The Realtime product that would be comparable would be either EMA API or Websockets - both of which allow sending a request once, and receiving multiple updates for that request, throughout the day. These however are different products and DSS credentials cannot be used to access it.


Categories