Error429 in ElektronTimeseriesExtractionRequest
Hi, I make 22 requests to the API every 10 seconds. And do this twice a day.
~~~~~~~~~~~~
- API URL : https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
- request_headers :
- "Prefer": "respond-async",
- "Content-Type": "application/json",
- "Authorization": "token " + MyToken
- body :
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions"
".ExtractionRequests."
"ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [
"Trade Date", "Open", "High", "Low",
"Last", "Ask", "Bid", "Volume"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions."
"ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": {
{product}}, #For example .SPX .N225 ....
"IdentifierType": "Ric"
}
],
"UseUserPreferencesForValidationOptions": "false"
},
"Condition": {
"StartDate": "{0:%Y-%m-%dT00:00:00.000Z}".format(datetime(1985, 1, 1)),
"EndDate": "{0:%Y-%m-%dT00:00:00.000Z}".format(datetime.now())
}
}
But rarely "HTTP 202 StatusCode" or "HTTP 429 Error" is returned. For 202code, it is solved by repeating the retry, but for 429error, the retry also fails.
Error code 429 | Client Error: Too Many Requests - Too many requests, please try again later.
Looking at other questions, there seems to be a limit (For example, 5 times per second). Please tell me all other limits.
Many thanks in advance.
Best Answer
-
mdt,
Yes, there are limits that apply to the API calls. If you exceed a limit, then you receive an HTTP status 429. To understand the limits I suggest you start by looking at the TRTH Best Practices and Limits document, as well as the extractions limit page.
That said, I am a bit intrigued by this statement: "For 202 code, it is solved by repeating the retry". A 202 is not an error, it is a normal message that occurs when a request takes longer than 30 seconds to extract all the data (which is a frequent occurrence). If you receive a 202 you should not repeat the request, as that adds an additional request in parallel that burdens the server. When you receive a 202 you should poll the location URL to detect when the extraction is complete. The workflow is described in the TRTH REST Tutorial 3. This is because requests are asynchronous (for more details, see the async help page).
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛