Error 202 with TickHistoryTimeAndSalesExtractionRequest
Hi,
I don't understand why I get a 202 error with the following code:
body = json.dumps({
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryTimeAndSalesExtractionRequest",
"ContentFieldNames": list_trade_fields,
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "SOLB.TG", "IdentifierType": "Ric" }
],
"ValidationOptions": {
"AllowHistoricalInstruments": True,
"AllowInactiveInstruments": True,
"AllowOpenAccessInstruments": False
},
"UseUserPreferencesForValidationOptions": False
},
"Condition": {
"ReportDateRangeType" : "Range",
"QueryStartDate": "2019-08-01T00:00:00.000Z",
"QueryEndDate": "2019-08-01T10:00:00.000Z"
}
}
})
url_post = "https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw"
header_post = {"Prefer": "respond-async, wait=30",
"Content-Type": "application/json",
"Authorization":myToken}
resp = requests.post(url_post,body, headers=header_post)
thank you for your help,
Tagged:
0
Best Answer
-
Hello @i.lucas, HTTP 202 is not an error code:
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.The server sent 202 because in your request you specified:
header_post = {"Prefer": "respond-async, wait=30",
This means that instead of keeping the client connection open for extremely long time, which can be dropped by network proxies/firewalls etc, the server waits 30 seconds and informs client that data isn't ready yet. After getting this response the client should wait and invoke another request for same URL until server responds with a HTTP200 OK message. Here is a snippet for doing that in python:
# is it a 202 (in progress)
while (resp.status_code == 202):
print("waiting...");
# check if the response completed yet
URL = resp.headers['Location'];
resp = checkStatus(URL);
print("Data available on server, fetching...");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 中文论坛