Hello @shyamala.k0 ,

Let us consider the first of the example - CMCU

In your Postman, please run the pattern as I have suggested:

{
"Request":
{ "RicPattern": "^CMCU[F-Z]{1}[0-9]{2}$",
"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"
}
}
}

Please observe CMCU instruments in the results, do you see them?

If they are getting CMCU back, but dates are nor working, please widen the Start and End dates, as we are out of April 22 now and out of May as well.

However, with their pattern, I do not get these results on my side either, please verify on your side?

Hello @shyamala.k0 ,

If you just looking for "unary" instruments like "CMALF23" please try

{
                {protocol}}{
                {host}}{
                {api}}Search/HistoricalCriteriaSearch 
{
"Request":
{ "RicPattern": "^CMAL[F-Z]{1}[0-9]{2}$",
"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"
}
}
}

, if for ranges as well, for example "CMALZ24-63PD", which I notice is also a valid instrument, try:

{
                 {protocol}}{
                 {host}}{
                 {api}}Search/HistoricalCriteriaSearch 
{
"Request":
{ "RicPattern": "^CMAL[F-Z]{1}[0-9]{2}",
"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"
}
}
}

Let me know if this is what you are looking for, otherwise please share a couple of example RICs that would match the desired criteria?

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.