Hello @shubham.x.kumar,

Tested, I believe, the same request via Postman tool:

{
                {protocol}}{
                {host}}{
                {api}}Extractions/ExtractRaw 
{
  "ExtractionRequest": {
    "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryRawExtractionRequest",
    "IdentifierList": {
      "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",  
      "InstrumentIdentifiers": [{
        "Identifier": "CARR.PA",
        "IdentifierType": "Ric"
      }]
    },
    "Condition": {
      "MessageTimeStampIn": "GmtUtc",
      "ReportDateRangeType": "Range",
      "QueryStartDate" : "2016-09-27T00:00:00.000Z",
      "QueryEndDate" : "2016-09-29T00:00:00.000Z",
      "ExtractBy": "Ric",
      "SortBy": "SingleByRic",
      "DomainCode": "MarketPrice",
      "DisplaySourceRIC": true
    }
  }
}

The result is pretty sizeable, 10.84M, so instead of "Send" button on the tool, I choose "Send and Download", and load it as a separate file.

The result includes two days of data, 27th and 28th and looks valid.

Suggest to try this request with Postman on your side, if you have not used Postman before, you may find Tutorials REST API Tutorials Introduction and REST API Tutorial 8: On Demand raw data extraction of help to review, the first one explains how to install and use Postman, the second on TickHistoryRawExtractionRequest, just modify the request that is part of the downloadable collection to your dates.

Hi,

Thanks for checking.

When I do this,

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

{"@odata.context":"https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#RawExtractionResults/$entity","JobId":"0x07576bb7c877120d","Notes":["Extraction Services Version 14.3.41935 (052f652420ba), Built Sep 4 2020 17:13:46\nUser ID: 9015812\nExtraction ID: 2000000201367162\nSchedule: 0x07576bb7c877120d (ID = 0x0000000000000000)\nInput List (1 items): (ID = 0x07576bb7c877120d) Created: 2020-11-26 07:24:18 Last Modified: 2020-11-26 07:24:18\nReport Template: _OnD_0x07576bb7c877120d (ID = 0x07576bb7c897120d) Created: 2020-11-26 07:23:14 Last Modified: 2020-11-26 07:23:14\nSchedule dispatched via message queue (0x07576bb7c877120d), Data source identifier (543CCB31AAA84094B2061A5596FC4FAD)\nSchedule Time: 2020-11-26 07:23:16\nProcessing started at 2020-11-26 07:23:16\nProcessing completed successfully at 2020-11-26 07:24:19\nExtraction finished at 2020-11-26 07:24:19 UTC, with servers: tm04n01, TRTH (47.643 secs)\nInstrument expanded to 1 RIC: CARR.PA.\nTotal instruments after instrument expansion = 1\nQuota Message: INFO: Tick History Cash Quota Count Before Extraction: 3; Instruments Approved for Extraction: 1; Tick History Cash Quota Count After Extraction: 3, 3% of Limit; Tick History Cash Quota Limit: 100\nManifest: #RIC,Domain,Start,End,Status,Count\nManifest: CARR.PA,Market Price,2016-09-27T01:25:00.679542394Z,2016-09-28T15:36:26.286749914Z,Active,192324\n"]}

Shows 192324 rows.

But this has only 67511 rows.

https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/RawExtractionResults('0x07576bb7c877120d')/$value

Hello @shubham.x.kumar,

Have you had a chance to confirm the size of the original request you have asked about, that I have verified for the exact response size? Did it match my result size?

---

For the last request, with the job id, if you would like to include the complete request, I will test it on my side.

If you would like to verify correctness by jobId, the moderators of the developers forum do not have access to client-run requests by jobId. But as a customer, you can verify the correctness of Tick History result content with Refinitiv product content experts, by opening a support case with Refinitiv Helpdesk Online -> Tick History

Hi,

I did check and its matching the results. I used a different rest api to query data and it worked.

Thanks for all the help and time.