Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TRTH /
avatar image
REFINITIV
Question by Manigandan.R · Jul 07, 2017 at 03:12 PM · tick-history-rest-api

It takes like 30 seconds to get the response back even after using respond-async. Could you please tell me how to decrease the time taken? Attached full query in detail - REST API

respond-async.txt

respond-async.txt (2.1 KiB)

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 veerapath.rungruengrayubkul · Jul 11, 2017 at 03:07 AM

@Manigandan.R

If you just want to decrease the response time when API returns the HTTP status 202 for asynchronous request, you can add the "wait" option in the Prefer header of the request message to chage the wait time. For example, "Prefer: respond-async, wait=5" means that it will respond either with the results, or with a 202 if the results could not be returned in 5 seconds.

For more information, please see the Async Key Mechanism page.


waitoption.png (23.1 KiB)
Comment

People who like this

0 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
REFINITIV
Answer by Christiaan Meihsl · Jul 10, 2017 at 08:05 AM

@Manigandan.R, the behavior you observe is normal, and there is nothing you can do to accelerate the time it takes for an extraction request to complete (apart from limiting its scope to what you need, i.e. limiting the number of instruments, data fields, and date/time range).

If the data is available in less than 30 seconds you will receive it directly. This is very rarely the case, most extraction requests take more than 30 seconds to complete. Your extraction is for 2 weeks of tick data, it will take several minutes to extract.

If the data is not available in 30 seconds an HTTP status 202 is returned, and you can subsequently check the status of the request by polling the location URL that is in the header of the 202 response.

For more details see the Async Key Mechanism page.

I also see that the date range for your query is in the future, no data will be returned. I tried your request, changing the year to 2016. The extraction took slightly less than 2 minutes.

Comment

People who like this

0 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.

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 >
10 People are following this question.

Related Questions

Working R examples for Eikon with Lipper data

Cannot retreive RIC list

If there is available SummaryInterval = 30 minutes aggregation in tick history intraday api?

Where can we see a list of the available report templates? (from Webinar May 31)

Specify the decade of the future contract

  • 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
  • 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
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges