Please suggest correct Refinitiv API call to be used

hariprasad.n
hariprasad.n LSEG
edited 2:59AM in DSS

Case # 14904659:

Hi Dev Team,

We need your advice on the correct Refinitiv API call to be used.

 What problem our client is facing: sometimes (5 cases for the last 6 months) the outdated file is taken from DSS, while the correct and actual one is already available. The latest scenario is the following:

 Our system (MarketView Sphere) has a job named “TRAF_LME_STOCKS”, that reads data from DSS “MV_TRAF_LME_STOCKS” schedule.

MV_TRAF_LME_STOCKS is triggered at 09:15 AM UK time daily (+30 mins embargoed period) on DSS side.

MV job TRAF_LME_STOCKS is triggered at 09:50 AM UK time daily.

MV Sphere uses API’s Last Extraction call to retrieve the last file for the schedule:

https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/Schedules('{scheduleId}')/LastExtraction

But on the 9th of June MV Sphere grabbed the previous file (from the 6th of June), when the actual one was already available. Could you please advise what correct API call should be used? And are there any issues in Last Extraction call that might cause such behavior?

image-4cfee72f2ae8f8-3b92.png

image-8114ba7d777cc8-5a7f.png

image-22b71d07f50568-9d18.png
Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @hariprasad.n

    Thank you for reaching out to us.

    This is a correct endpoint to get the last completed report extraction for a schedule. For example:

    https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/Schedules('0x07b1b9370a7d1892')/LastExtraction

    The notes indicates that the data has been embargoed.

    image.png

    Please contact the DataScope Select support team directly to investigate this issue.

Categories