We are continuing to have issues using the PermId Search API showing erratic behaviour.

For example, when calling the following API many times in a row:

https://api.thomsonreuters.com/permid/search?access-token=XXXX&entityType=quote&q=ticker:COH AND mic:XASX

Sometimes we receive the correct result:

{ "result": { "quotes": { "entityType": "quotes", "total": 1, "start": 1, "num": 1, "entities": [ { "@id": "https://permid.org/1-55835577616", "hasName": "COCHLEAR ORD", "assetClass": "Fully Paid Ordinary Shares", "isQuoteOfInstrumentName": "Cochlear Ord Shs", "hasRIC": "COH.AX", "hasMic": "XASX", "hasExchangeTicker": "COH", "isQuoteOf": "https://permid.org/1-8590940165" } ] } } }

and sometime we receive:

{ "result": { "quotes": { "entityType": "quotes", "total": 0, "start": 1, "num": 0, "entities": [] } } } In both situations we receive a status code of 200 (OK)

This has been acknowledged previously as a bug and we were wondering what the timeframe on this being rectified is?

Regards,

David