Due to migration tempates on DSS side some endpionts will no longer be supported (e.g. SOAP - InstrumentExtractionRequestTimeSeriesPricing ).
Currently we use TimeseriesPricing template and the new suggested is PriceHistory.
We would like to know the impact on our communication channels and information what we should changed on our side. This information is not clear to us and impacts production.
Our project (TSRD) uses FTP, SOAP and REST api to communicate with DSS. Please provide what should be changed on our side. Here is the list of our communication channels to DSS
So far we know that SOAP (InstrumentExtractionRequestTimeSeriesPricing) should be repalced by RestAPI(
https://hosted.datascopeapi.reuters.com/RestApi.Help/Context/Operation?ctx=Extractions&opn=ExtractWithNotes&sce=On Demand Extractions - Create - Price History.primary&tab=2)
This is urgent Credit Suisse production issue with communication to DSS.
On TimeSeries Rest access, I believe this requires action. Legacy TimeSeries removal was first announced in Nov 2019 Release Notes for Feb 2020, to be replaced with PriceHistory and SinglePriceHistory. It was later postponed, and finalized for Sept 2020. In Release Notes linked you will find the info on the relevant product PCNs with the complete and detailed info. Please find REST API Tutorial 4: On Demand price history extraction to aid you to integrate easily.
On FTP I have not seen any migration notices, on my side. In terms of single type of access vehicle, and convenience, it may make sense to look into uniform REST design approach at the time of the TimeSeries change.
I would suggest to bring up any urgent DSS product questions or issues by submitting a product support case on Refinitiv Online Helpdesk -> DSS or over the phone to local Refinitiv Helpdesk, so that your inquiry may be addressed in the urgent manner. Refinitiv developers forums are most effective for general Refinitiv API-centered questions and discussions.