How to resolve RTH API - Historical criteria search - Regex codes errors

Hello @shyamala.k0 ,

Historical Criteria Search regex implements limited regex matching- it is not the complete regex spec.

It would be helpful to share an example of one or two RICs, that the client and you are looking to match?

Please also see this previous discussion thread for the approach ideas.

Hello @shyamala.k0 ,

Having confirmed that you are looking for singular instruments, for example "CMCUM22", and because HistoricalCriteriaSearch implements limited regex, I would run 4 separate RicPattern searches:

 "RicPattern": "^CMAL[F-Z]{1}[0-9]{2}$"
 "RicPattern": "^CMCU[F-Z]{1}[0-9]{2}$"
 "RicPattern": "^CMNI[F-Z]{1}[0-9]{2}$"
 "RicPattern": "^CMZN[F-Z]{1}[0-9]{2}$"

Let us know how this works for you

subscriptionListWithReceivedRICs_new.txt

We were able to get only 148 symbols for the date 6^th of Jun, with the suggested pattern (Example "RicPattern": "^LCO[F-Z]{1}[0-9]{2}$")

We gave another round of try, now combining both the pattern for 7^th of Jun 2022 and we are able to get bigger range of products(Example : ^LCO[FGHJKMNQUVXZ][0-9]$|TYO|FUT and ^LCO[F-Z]{1}[0-9]{2}$

Hello @shyamala.k0 and @ashok.kumar.murahari.1 ,

Apologies for the belated response, I was out of the office.

You may have had a chance to observe, that if you apply criteria as:

{
"Request":
{ "RicPattern": "^LCO[FGHJKMNQUVXZ][0-9]$|TYO|FUT",
"BondTypeCodes": null,
"ContributorIds": null,
"CountryCodes": null,
"CurrencyCodes": null,
"ExchangeCodes": null,
"FutureMonthCodes": null,
"InstrumentTypeCodes": null,
"OptionMonthCodes": null,
"OptionTypeCodes": null,
"CouponRate": null,
"StrikePrice": null,
"ExpiryDate": null,
"MaturityDate": null,
"Range": {
"Start": "2022-05-17T00:00:00.000Z",
"End": "2022-05-18T23:59:59.999Z"
}
}
}

You get more hits, but please examine the results, are these the hits that you require:

{
    "@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalSearchResult)",
    "value": [
        {
            "Identifier": "FUT",
            "IdentifierType": "Ric",
            "Source": "",
            "Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxGVVR8",
            "Description": "Historical Instrument",
            "InstrumentType": "Unknown",
            "Status": "Valid",
            "DomainCode": "6",
            "FirstDate": "2004-03-30T00:00:00.000Z",
            "LastDate": "2022-05-03T00:00:00.000Z",
            "History": []
        },
        {
 "Identifier": "FUT.A",
            "IdentifierType": "Ric",

I believe they are not.

If you are looking to retrieve results as per requirement communicated by @shyamala.k0 , I suggest running 4 requests with patterns as above, for clarity, and next, combining the 4 results. This should produce the results per your requirements.

The regex that is supported by service is not the full regex spec . In my observation, "|" inside stanzas is not fully supported, and when used, leads to random results. Which is why I would not combine the patterns in the request, via "|", but combine the results.

I hope that this information helps.

I would not be able to confirm why there were only 148 results on a specific date. Refintiiv content experts will be able to help with this type of question about content, and if posted to Refinitiv Helpdesk Online, the expert for type of content in question will be assigned to help.