How can we request the CommoditySearch API for the particular ric code?

RIkesh
RIkesh Newcomer
edited May 6 in DSS

The request body for the request is as in the code block below. Here, we are receiving the response with unwanted Identifier value such as 'D-NGMMH25' with prefix 'D'? How can we get only the valid Identifier assigned to our user.

{

    "SearchRequest": {

        "KeywordQuery": "NGMM",

        "ExpirationDate": {

            "@odata.type": "#DataScope.Select.Api.Search.DateRangeComparison",

            "From": "2025-04-28T00:00:00.000Z",

            "To": "2026-04-29T00:00:00.000Z"

        },

        "PreferredIdentifierType": "Ric",

        "AssetStatus": "Active"

    }

}
image.png
Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @RIkesh

    Thank you for reaching out to us.

    In the request, you may need to exclude the "PLT" exchange code. 

    {
    
    "SearchRequest": {
    
        "KeywordQuery": "NGMM",
    
        "ExpirationDate": {
    
            "@odata.type": "#DataScope.Select.Api.Search.DateRangeComparison",
    
            "From": "2025-04-28T00:00:00.000Z",
    
            "To": "2026-04-29T00:00:00.000Z"
    
        },
            "ExchangeCodes":["PLT"],
    
        "ExchangeCodesOperator":"Exclude",
    
        "PreferredIdentifierType": "Ric",
    
        "AssetStatus": "Active"
    
    }
    
}

    However, please contact the DSS support team directly via MyAccount to verify this request.

  • RIkesh
    RIkesh Newcomer

    Hi @Jirapongse ,

    Thank you for the answer. It does filter out the unwanted RICs. However, could not get the price value for the RIC received in the response. The response ss is below

    image.png

    Can you also provide brief detail about the use of Chain Ric for the above case?

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @RIkesh

    It looks like to be a permission issue. Please contact the DSS support team directly via MyAccount to verify data and permission.

    image.png

    Typically, chain RICs can be used in the request. For exmaple:

     "IdentifierList": {
    
      "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
    
      "InstrumentIdentifiers": [

          	{ "Identifier": "0#ARGACHHNG:", "IdentifierType": "ChainRIC" }
    
      ]
    
    },
  • RIkesh
    RIkesh Newcomer

    Hello @Jirapongse,

    The JSON request body referenced in the above question functioned correctly until early January 2025, at which point the response data unexpectedly altered. Do you have any idea regarding potential logical changes that may have occurred?

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    https://community.developers.refinitiv.com/discussion/comment/125647#Comment_125647

    If you mean the permission one, please contact the DSS support team directly via MyAccount to verify what the problem is.

  • RIkesh
    RIkesh Newcomer
    https://community.developers.refinitiv.com/discussion/comment/125651#Comment_125651

    Not the permission, but the response data. It seems to work fine for other RIC codes; the problem seems to be with RIC code 'NGMM' only.

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    If it is about the "KeywordQuery": "NGMM", the following is the definition of "KeywordQuery".

    Property Name="KeywordQuery" Type="Edm.String"><Annotation Term="Org.OData.Core.V1.Description" String="Searches multiple fields for a value."/><Annotation Term="Org.OData.Core.V1.LongDescription" String="The fields searched are identifier, description, long description, file code, and lot units."/>

    It returns D-NGMMH25 because it contains NGMM in its name.

Categories