DSS request inconsistent timeout
Hi ,
We are POSTing the following request for DSS API.
- We are requesting every 5 minutes.
- We waiting for a minute before we timeout the request.
- About 15 times a day it takes more then a minute (and then I fail the request).
-- Is it ok and normal that sometimes it takes more then a minute ?
-- Am i doing something wrong ?
-- Should i increase the timeout ?
Here is the request :
curl -X POST \
https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes \
-H 'Authorization: Token XXXXXXXXXXXXX’ \
-H 'Content-Type: application/json' \
-d '{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.IntradayPricingExtractionRequest",
"ContentFieldNames": [
"RIC", "Mid Price", "Security Description", "Instrument ID", "Instrument ID Type"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "EUR=", "IdentifierType": "Ric" },
{ "Identifier": "CNYUSD=R", "IdentifierType": "Ric" },
{ "Identifier": "JPYUSD=R", "IdentifierType": "Ric" },
{ "Identifier": "GBP=", "IdentifierType": "Ric" }
]
},
"Condition": { "ScalableCurrency": "true" }
}
}'
Best Answer
-
Q1: Is it ok and normal that sometimes it takes more then a minute ?
A1: Yes, server response times vary depending on the size of a request, and on the server load.
Q2: Am i doing something wrong ?
A2: You should not resubmit your query after a timeout; it increases the server load, because when you resubmit, you have 2 queries running in parallel. Instead, you should check the status of the existing query, by doing a GET to the location URL that is returned in the header response when it times out (the response that has an HTTP 202 status). For more information on this workflow, please see:
- The DSS REST tutorial 2 (you can also download our Postman collection to see exactly how it is done)
- The async key mechanism help page
Q3: Should i increase the timeout ?
A3: As per the answer to your previous question, no, that is not the way to handle a request that times out. As a side effect this would also delay the time it takes to receive your data (as you are requesting intraday data I guess you want it fairly quickly). You need to handle the 202 response if you run into a timeout. I would actually revert to the standard default timeout of 30 seconds.
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 中文论坛