@zoya.farberov and @mohamed.hisham Hi, I would recommend to increase the results by keying in header as below:

Prefer: respond-async;odata.maxpagesize=100000

Here is the output showing CLK1

Hello @mohamed.hisham,

Let me try to answer, with a little disclaimer- I am a developer, this forum is dedicated to general questions and discussion of Refinitiv API usage, and Refinitiv content experts are best reached directly via Refinitiv Helpdesk Online -> Content

Having tested this search via Datascope GUI client, it's a giant search. The result does not fit into the maximum DSS GUI search result size of 5000 instruments:

so to me, this indicates that not the complete search results will be returned, and this request is not a good candidate for this InstrumentSearch request, the request is too wide, in order to obtain a complete result, one would have to narrow down the request.

One way to quickly verify that this Ticker maps to this RIC is running the opposite request, RIC -> Ticker

{
  "SearchRequest": {
"InstrumentTypeGroups": [
"FuturesAndOptions"
],
"IdentifierType": "Ric",
"Identifier": "CLK1",
"PreferredIdentifierType": "Ticker

And result is as expected:

 {   "@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Content.ValidatedInstrument)",
    "value": [
        {
            "Identifier": "CL",
            "IdentifierType": "Ticker",
            "Source": "NYM",
            "Key": "VjF8MHgwMDEwMGIwMDBkZmVkZWVhfDB4MDAxMDBiMDAwZGZlZGVlOXxOWU18RFZRVXxERVJWfEZVVHxEfHxDTEsxfDUwMzQ",
            "Description": "LIGHT CRUDE MAY1",
            "InstrumentType": "DerivativeQuote",
            "Status": "Valid"
        }
    ]
}

Now we have confirmed that Ric CLK1 maps to Ticker CL.

Going back to narrowing down the request, I would look into

FuturesAndOptionsSearch that is more suitable for futures and options then InstrumentSearch,

and try to narrow it down by F&O specific parameters. This search does not accept Ticker as IdentifierType parameter, so the correct way to the search is less then obvious to me, may require two requests.

However, Refinitiv DSS content experts should be able to better guide you on this, to help identify the appropriate search for your requirements, which you can then run via API.

I know this is not all the information you are looking for, I hope this helps to progress toward the solution.