I have a UPA application which can request TAS data by requesting the TAS symbol for a RIC e.g. tVOD.L. I was wondering what do I request to get the equivalent data now that TAS support is being discontinued.
163
●11 ●11 ●19
Requesting TAS data.
Hello @andy.sciascia
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hello @andy.sciascia
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
32.2k
●40 ●11 ●20
The suggested options to get this data for API clients are migrating to Tick History, Data Scope Select, TRKD or Eikon, based on the use case. All these options take time and effort to plan and implement.
For Eikon GUI clients only, users will continue to can get this content by right clicking on RIC in Eikon.
This is a bit late to plan migration from TAS for API uses (UPA), in my understanding, as scheduled removal date is tomorrow, Sept 30th.
This could be an issue for you, depending on the use and how critical the application is for your organization I would get in touch with TR account management team ASAP to work out the best course of action this late in the game?
Hope this information helps to clarify and allows to progress toward the solution,
-AHS
163
●11 ●11 ●19
TAS is being retired but I assume the equivalent data for the RIC's is available by requesting another symbol using a UPA API. Is that correct ? Also, I've looked for references to Tick history in the 8.0 UPA API doc and I can't find any.
32.2k
●40 ●11 ●20
No, there will be no replacement symbology that can be accessed by UPA. This content will not be available from Elektron, our realtime infrastructure.
This, and much more more depth and breadth of content, are be available from history and analytics products, i.e. Tick History, Data Scope Select, TRKD or Eikon.
These products are accessible via different API, for examaple, for Tick History, it's Tick History REST API, for Eikon, it's Eikon APIs, please review the corresponding materials on this portal.
This is why it's a bit late, and the best course of action would be putting heads together with your account management team and planning the optimal migration path, then implementing the programmatic solution.
163
●11 ●11 ●19
Ahh - ok. That's the bit I didn't understand. So basically a UPA application will no longer be able to access this data. That's the main thing I needed to know.
163
●11 ●11 ●19
By the way - just to clarify. TAS is being removed tomorrow, so I assume that if I request tVOD.L or t<anything> after tomorrow then I'll get not found as the response ?
32.2k
●40 ●11 ●20
I would say that after September 30th, 2017, there will be no guarantee that you will be able to call subscibe to tRICs, for example tVOD.L
