Requests: Single Price History and Price History
Hi,
We have a question about the changes in templates coming in February 2020.
Currently we are using these GETs to request information from several Templates that are: “Timeseries Pricing and Single Historical Price” format and we need to change it to Single Price History and Price History, and we need to migrate that from API SOAP to REST API.
This migration will have impact on these POST/GET requests?
We need to update them, or just create new templates with the new format (Single Price History and Price History) and name them like than the old ones?
We are doing these requests to the API.
- POST - https://hosted.datascopeapi.reuters.com/RestApi/v1/Authentication/RequestToken
- GET - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ReportTemplateGetByName(Name='XXXXXX')
- GET - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ReportTemplates('XXXXXXX')
- POST - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
According to the list of requests you are using, both extraction types are used.
- Schedule extraction - It seems that your application uses existing Report Templates created in DSS to extract data. You can create new Report Templates with the old names using Single Price History and Price History template.
- GET - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ReportTemplateGetByName(Name='XXXXXX')
- GET - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ReportTemplates('XXXXXXX')
- On Demand extraction - You need to change the request body to use the new Report templates and fields.
- POST - https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
As part of the migration process, it is important to understand that, in some instances, field content extracted from the Timeseries Pricing and Single Historical Price reports will be available under different field names in the Price History and Single Price History reports. Please find more details on the migration and the required client action in this Product Change Notifications