question

Upvotes
Accepted
rahul_srivastava avatar image
3 ●1 ●2 ●5

REST API TRTH working slow

Hi,

I am trying to download the intraday report for RICs as of 29th Nov 2017, and it seems the API is working slow. For reach RIC I have to make at least 30 poll (30 sec wait between each poll). Do you know if the API has some problem. 30 polls seems a bit slow for downloading 1 day report for 1 RIC.

Also since we would be deploying our code in Production environment soon. I need to understand below points -

1) in case the API is responding slow, Is there a way we can request you to investigate on root cause? What all details you would be needing from our side in order to dig down to the log for all request made by our application?

2) From validation point of view, is there a way I can know in advance the total count of records for intraday summary report? For e.g., lets say for a RIC "ABC" when I download data for a day; I get 1000 rows. Is there a way I can validate if 1000 rows are all that was available or we missed anything?

3) Can I provide the Job ID which we use to poll the to get the extraction to find out more from your end about the slowness of API?

4) How many poll attempts should I make before considering its a timeout? I do not want my process to run forever in case the API is down or something.

tick-history-rest-api
icon clock
10 |1500

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

rahul_srivastava avatar image rahul_srivastava

Just to add to my question - I tried for 30th Nov for RIC - 1ZEK0

here is the Job location. I have made 43 poll attempts as of now. and I still do not see response status as 200.

1st poll attempt was made at 12/04/2017 11:44:01 EST

43rd poll attempt made at 12/04/2017 12:28:03 EST

https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x05f967ba2f2b3036')

1 Answer

Upvotes
Accepted
zoya faberov avatar image
23k ●22 ●9 ●14

Hello @rahul_srivastava,

1) & 3)

When we suspect something is off with service, the first place to check is

My Account - Notifications - Service Alerts

Today I see 167753:

DataScope Select Tick History 2.0 and On Demand REST API Extractions - Potential Delays

In the more common case where there are no service disruptions, and you find that a specific request is not behaving the expected way, the best way to investigate is to Open a Service Request with product = Tick History V2, provide your job ID and have us take a look at it.

2) Check "Notes". If there are any issues with the specific request, such as invalid, not completed, etc., it will be reflected in the extraction notes.

4) There is no universal rule on timeout that I can suggest. The time to complete a request depends on the request.

Personally, would make sure the request is valid, i.e. "Accepted", and after that, depending on the usual expectation for this type and size of the request, and if there are no service disruption, I would give it double or triple this time.

icon clock
10 |1500

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

Click below to post an Idea Post Idea