PriceHistoryExtractionRequest

According to the DataScope selected user guide (https://developers.refinitiv.com/sites/default/files/DSS_13_0_User_Guide.pdf)
"Individual user accounts are permitted to execute only one Price History extraction at a
scheduled time. Simultaneous Price History extractions from the same user account are not
allowed to ensure resources are available for all user accounts at any given time."
Does this mean that we can only submit one extraction request at a time? I ran the two requests (listed below) simultaneously against /RestApi/v1/Extractions/ExtractRaw API and was able to successfully retrieve extractions.
***I have only included a small set of IdentifierList, I have tested with a 1000 count of Identifiers
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest",
"ContentFieldNames": [
"RIC",
"Trade Date",
"Universal Close Price"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"IdentifierType": "Ric",
"Identifier": "GLL"
}
]
},
"Condition": {
"AdjustedPrices": false,
"QueryStartDate": "2019-02-02",
"QueryEndDate": "2019-02-03"
}
}<br>
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest",
"ContentFieldNames": [
"RIC",
"Trade Date",
"Universal Close Price"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"IdentifierType": "Ric",
"Identifier": "AAPL.O"
}
]
},
"Condition": {
"AdjustedPrices": false,
"QueryStartDate": "2019-02-02",
"QueryEndDate": "2019-02-03"
}
}
I have a use case where I need to post 2000 instruments and given the limitation of the instrument size (max of 1000) I want to submit two simultaneous request to fetch the extract. Is this possible or will I have to wait until the first is completed?
Best Answer
-
The limit on simultaneous requests is for concurrently running requests. That means that, for a Price History extraction request (which has a limit of 1), you should wait for the first request to complete before submitting the second request.
I am a bit surprised you managed to submit 2 requests in parallel. They both have 1000 RICs, but on the other hand they have few fields, and a small date range. It could be that, even though you submitted them one just after the other, the first one completed before the second one was queued ? That's just a guess. But in any case this might not work every time.
In conclusion: to ensure your code is reliable I strongly recommend you submit the first query, wait for it to complete, and then submit the second one.
0
Answers
-
@Christiaan Meihsl
Thanks for the response. To make sure I understand this correctly as soon as I receive a 200 HTTP response code from the /ExtractRaw API the query is considered completed correct? This isn't coupled with the raw extraction fetch api correct (i.e the /
0 -
yes, when you receive an HTTP 200 the request is complete.
Note the 200 could be either from the POST to ExtractRaw, or a subsequent GET to the location URL (if ExtractRaw returned a 202).
You can actually see that in the extraction Notes, which should contain entries "Processing completed successfully at" and "Extraction finished at".
In case of need, the entire workflow is described in REST API Tutorial 14.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛