Why the url’s structure is different in the 202 Status case TRTHv2 REST API

Beera.Rajesh · June 2017

I ran an ElektronTimeSeries(EndOfDay) request.

The response I got is :
Status Code – 202
‘Location’ in Headers - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x05c454b16eab3026')

However, In the docs Chapter 10, I see that the Location URL when the status code is 202 should be like the following –
‘Location’ in Headers: https://hosted.datascopeapi.reuters.com/RestApi/v1/monitor/'0x0570a0ea31ec3156'
If a GET is requested on this Monitor URL, and if the status is 200, we would get the extractRawResult URL.
Is My Understanding correct?
If Yes, Why did I get the ExtractRawResult Location directly with 202 status code?

Why the url’s structure is different in the 202 Status case.

One contains the word ‘Monitor ‘ - https://hosted.datascopeapi.reuters.com/RestApi/v1/monitor/'0x05709cc5aadc3156'

And Other contains the ‘ExtractionResults’ -https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x058dcda3c29b5841')

Both the above URLs correspond to the 202 Case.

Jirapongse · June 2017

The Location URL in the document may be outdated. To check the status, you need to use the URL shown in the "Location" header with GET method such as GET: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x05c46af2ef4b3026').

Once the status is 200, you will get the response with "JobId" which is the same number as ExtractionId.

{
    "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#RawExtractionResults/$entity",
    "JobId": "0x05c46af2ef4b3026",
    "Notes": [
        "..."
    ]
}

After that, to get the data, you need to use GET method with https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/RawExtractionResults('0x05c46af2ef4b3026')/$value.

You can download and use TRTH REST Tutorials Postman collection tool to verify the behavior. You can download Postman from https://www.getpostman.com/.

Why the url’s structure is different in the 202 Status case TRTHv2 REST API

Best Answer

Categories

EXPLORE OUR SITES

Why the url’s structure is different in the 202 Status case TRTHv2 REST API

Best Answer

Categories