How can you get a list of available scheduled extracted files and download them via API by file n...

@alvaro.canencia, let me attempt to answer your queries:

Q1. How can I get those 'schedule ids' for my scheduled reports?

A1. There is
a call to list all schedules (it returns them all, not only the active
ones):

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/Schedules

The response includes (among other fields) the ScheduleID. You can run this example in the C# example app (its installation and usage are described in the Quick Start), it is the first one in category Schedule Examples. As far as I know this should only return "Stored and Scheduled", not "On demand".

Q2. With the schedule id I got from the GUI I've tried to use the urls you provide, substituting the '123' with the 'schedule id' from the GUI. None of the urls work. I get the message: "Resource not found for the segment 'Schedule'"

A2. Using Schedule IDs, the workflow is:

a) Check each scheduled extraction status using its ScheduleID (retrieved as explained under A1 above):

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/Schedules('0x05a2b98d233b3036')/LastExtraction

Repeat until the returned status is "Completed", then save the returned ReportExtractionId

As your schedules are daily, you do this daily after your schedules should have triggered, at a point in time when you expect them to have completed.

b) Retrieve the corresponding extraction report, using the ReportExtractionId:

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ReportExtractions('2000000000197524')/Files

Save the returned ExtractedFileId you are interested in, for each file you want. I fully agree with Troy, you should not only download the data file, but also download the Note file, because it contains useful information on the extraction, eventual errors or warnings, etc.

c) Retrieve the files, using their ExtractedFileId:

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractedFiles('VjF8MHgwNWEyYjk5ODRiNmIyZjk2fA')/$value

These steps are all described in detail in REST API Tutorial 12. As you created your instrument lists, templates and schedules manually, you can skip the first steps of that tutorial, and start directly at step Check the extraction status, which corresponds to step a) in this answer.

Alternative using file names

You could choose to ignore the schedules completely, and just look at the extracted files.

You can simply get the latest extracted files extraction for all schedules. The call delivers the file ID, report extraction ID, schedule ID, file type, file name, timestamp, size, etc.

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractedFiles

After that you can get the changes to that list (using the delta token returned by the previous call).

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractedFiles?$deltatoken='MjAxNy0wOS0wMVQxNTo0MjoxNi4yNzAwMDAwfDB4MDAwMDAwMDAwMDAwMDAwMCwzMTUyMjUyNjg'

Finally, you can proceed to get the files, using the returned file ID(s):

GET https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractedFiles('VjF8fDMxNTIyNzYzOQ')/$value

Note you can run the calls I list here under Scheduled Extractions in the C# example app (described in the Quick Start).

Conclusion

There is no "best way", it really depends on your workflow and you own preferences.

Hope this helps.