Datascope select monitoring api respond-async wait time
Hi,
I am building a system to process hundreds of requests for many different users, for the Datascope select api for TickHistoryTimeAndSalesExtraction. My plan is to handle asynchronicity in the application by calling the monitor api (i.e. /RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x123456789')) every 30 seconds, until receiving a 200 response. To achieve that I am setting the "prefer" http header, with a value of "respond-async, wait=1". However, I am finding that the response always takes at least 30 seconds (unless the extraction is completed). This is a problem, as I do not want to keep hundreds of concurrent http connections open for the 30 seconds each.
Is this the expected behaviour for this api?
Note, I have found that the "respond-async, wait=1" works as I would expect for the initial "ExtractRaw" request.
Many Thanks
Best Answer
-
Thank you for reaching out to us.
I tested and found that for polling a location URL, the mininum value of wait time is 30 seconds.
If I set the wait time to less than 30 seconds, it will use 30 seconds.
However, if I set the wait time to more than 30 seconds, it will use the value in the wait time.
1
Answers
-
@Jirapongse Thanks for the reply. It's good to note that you are experiencing the same behaviour as me. Is this behaviour intentional? Do you know the reason for it? It seems unusual to me and limits the flexibility of the consumer. It means that my application now has to wait for a minimum of 30 when making the first monitoring request following an extraction request. Do you have any recommendations to mitigate this? Thanks.
1 -
Please contact the DSS support team directly via MyRefinitiv to confirm this behavior.
I found this statement in the Async Key Mechanism.
Prefer: respond-async, wait=120 The default wait/poll time is 30 seconds. The API uses long polling, which means that it will respond either with the results, or with a 202 if the results could not be returned in 30 seconds. We do not recommend changing this value. Changing the value will not result in getting results more quickly. In fact, more frequent polling, by reducing the poll time, will incur an additional overhead and a slight reduction in the response time.
0 -
I am also interested in this! We use a serverless architecture and would prefer not to pay for our Cloud Functions or Lambdas to just wait on an API response!
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛