Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • DSS /

For a deeper look into our DataScope Select REST API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials

avatar image
Question by elvis.fernandez · May 06, 2019 at 04:50 PM · dss-rest-apidatascope-selectdssricsapi-limits

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?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Christiaan Meihsl · May 07, 2019 at 04:27 AM

@elvis.fernandez,

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.

Comment
elvis.fernandez

People who like this

1 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Answer by elvis.fernandez · May 07, 2019 at 03:35 PM
@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 /

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
REFINITIV
Christiaan Meihsl ♦♦ · May 08, 2019 at 04:15 AM 0
Share

@elvis.fernandez,

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.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
11 People are following this question.

Related Questions

The limitation of a instrument list

How would you suggest we download large files (2015 is 157 gb. Even if we split it by month, we wouldn’t be able to download the data)

What is the difference between RIC Codces that end with =X?

Filter out Continuation RIC in a Terms and Condition extraction request result

Most cost effective way to figure out a primary RIC from an ISIN (or other identifier)

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • FX Venues
    • FX Trading – RFQ Maker
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • Yield Book Analytics
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges