@Francesco.De.Venuto

Typically, the error 429 indicates that the application exceeds the request limit of the endpoint. For example, the interday-summaries endpoint limits 50 outstanding requests at a time and 50 requests allowed in one second.

You may split four thousand RICs to multiple requests.

Otherwise. you can enable logging in the API to verify what the problem is. Add the following configuration to the RD configuration file (refinitiv-data.config.json).

{   
  "logs": {
    "level": "debug",
    "transports": {
      "console": {
        "enabled": false
      },
      "file": {
        "enabled": true,
        "name": "refinitiv-data-lib.log"
      }
    }
...
}

The refinitiv-data-lib.log file will created in the current directory.

Please refer to the example on GitHub how to load the configuration file. For example:

import os
os.environ["RD_LIB_CONFIG_PATH"] = "../../Configuration"

Hi @Francesco.De.Venuto ,

I'm afraid that this errror is instrument specific. What I mean is that it may come up depending on the RICs in the `universe`. The best way to see this is by using different instrument types, e.g.:

rd.get_history(
    universe=["USDSR3L10Y=", "LSEG.L"],
    fields=['BID','HIGH_1', 'LOW_1','MID_PRICE','ASK','ASK_HIGH_1', 'ASK_LOW_1', 'TR.ClosePrice'],
    start = '2022-12-31',
    end = '2023-06-30',
    interval="daily"
    )

In this example, "LSEG.L" returns 'TR.ClosePrice' data, but "USDSR3L10Y=" does not.

The best way to check if there is data for the fields you are after, for the instrument you are after is via the Data Item Browser. Have you tried using it?