Symbology API

Hi I have two questions about the Symbology API:


1) In Beta1 version, you had the following call:

https://api.refinitiv.com/data/symbology/beta1/convert?universe=4295890634

This convert call does not seem to exist in the Beta 2 version of the API. Why is that? What is the replacement call that will bring the same fields in the response?


2) How many instruments the symbology API ( as the example above) can handle in one request?

Our intention is to select all the 8K companies that we get with the ESG API ( GetUniverse call) and convert the Organization Permids into LEI codes. How can we achieve that? Is it possible to request all companies with one symbology request?


Best regards,

Carlos Feres

carlos.feres@avaloq.com

Best Answer

  • zoya faberov
    zoya faberov ✭✭✭✭✭
    Answer ✓

    Hello @carlos.feres3 and all,

    Would like to share additional information:

    Beta 1 –
    provides symbology and some core company/primary instrument and quote reference
    data for ESG API users

    Beta 2 – provides specific point to point symbology navigation routes (e.g. ISIN to Issue PermID) for general use and does not contain any reference data. ISIN to LEI route is not supported on Beta 2

    Core
    Symbology API – scheduled to be release early September 2020 will be successor
    for Beta 2 and allow user to define their own start/end point for identifier navigation,
    but contains no reference data

    For now we recommend using beta 1:

    Beta 1
    handles 100 identifiers per request, therefore, larger request lists would need to be looped

    For future:

    Core
    Symbology API, road-mapped to be launched later in the year, will be able to navigate from
    Organization PermIDs to LEIs in much larger numbers in one request.

Answers

  • zoya faberov
    zoya faberov ✭✭✭✭✭

    Hello @carlos.feres3,

    Try

    https://api.refinitiv.com/data/symbology/beta2/lookup

    On limits, I am not fully certain, used to be 100 instruments per single request, so you would need to loop through the target request list of 8k.

  • Hi Zoya,

    Thanks for the more complete answer. Can you clarify how exactly these versions ( beta1,beta2, etc) are managed?

    We are EAP participants but we will develop functionality in the next quarters based on the current API calls available in RDP. I thought any calls in Beta1 version not carried to Beta 2 is basically functionality that has been dropped. Is this not the case? Can we count that Beta 1 will remain productive? What is the process to be informed about new and retired functionality within Symbology/RDP?


    Thanks for the feedback,

    Carlos


  • zoya faberov
    zoya faberov ✭✭✭✭✭

    Hi Carlos @carlos.feres3,

    The news on API and releases information is communicated by product management in News and Updates sections, for RDP APIs, see RDP News and Updates.

    Additionally, developers have an option to register to "Watch" a specific API, consequently, get an email notification of any News & Updates published item for the specific API (RDP).

    Both beta versions will exist for a period of time.

    Per product management, the general release version will be made available at some point of time.

    Per product management, beta versions will be retired at some point of time.

    The functionality is being improved and enhanced based on developer experience and feedback collected during beta period.


  • zoya faberov
    zoya faberov ✭✭✭✭✭

    Hello @carlos.feres3 and all,

    Although Core will replace Beta 2. The Beta 1 version will continue on into 2021. Beta 1 has functionality (e.g. reference data retrieval) that is not replaced by Beta 2 or Core, so we are aware that Beta 1 needs to be supported ongoing until that functionality Is available elsewhere in the platform. We make announcements about changes to content and products via my.refinivit.com, for symbology APIs we will also provide links to those notifications in the developer portal.

    Here is an (unrelated) example of a product notification in the developer portal with the link to example link