Receiving 429 responses too often
I find I am receiving 429 responses all too often. I have limited my code so that it won't make a request more often than every 2 seconds.
I have added log lines to my code for every time it makes a request:
These are the only requests I have made inside this time period:
2019-02-08 15:28:18,291 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
2019-02-08 15:28:22,500 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
2019-02-08 15:28:26,774 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
2019-02-08 15:28:30,969 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
2019-02-08 15:28:35,187 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
2019-02-08 15:28:39,410 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
2019-02-08 15:28:52,400 - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
But the request at 15:28:39,410 received a 429 response:
2019-02-08 15:28:39,410 [pool-6-thread-1] - actualMakeCall: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRaw
2019-02-08 15:28:50,349 [pool-6-thread-1] - this is httpstatuscodeexception: {"error":{"message":"Failure reason: UserExtractionLimitExceeded: 9019523 has 2 ET2 extractions, limit is 2"}}
Best Answer
-
you cannot submit a request until the other one has completed.
From the Best Practices and Limits document page 9:
When a user reaches his or her limit for the number of extraction requests for a report template type, any
additional extraction request that he or she submits against that template type will fail, with the extraction
notes explaining why it failed. If the user submitted the request via the REST or SOAP API, the over-the limit request will return HTTP status 429 with a description of the problem. Once any request ends, the tally of submitted requests is reduced by one, enabling the user to successfully submit an additional
request.0
Answers
-
Is this actually unrelated to HTTP requests? Is this actually that I can't have more than two requests in the queue at the same time?
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 中文论坛