Hello @krishna muppavarapu,

Providing current error codes on authentication request from API Playground:

Responses

Response content typeapplication/json

CodeDescription200

OK

• Example Value
• Model

{  "access_token": "string",  "expires_in": "string",  "refresh_token": "string",  "scope": "string",  "token_type": "string"
}

400

Authentication error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

401

Authentication error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

403

Authentication error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

500

Internal server error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

502

Upstream server error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

504

Upstream server error

• Example Value
• Model

{  "error": "string",  "error_description": "string",  "error_uri": "string"
}

In addition, if you have an EDP product, and the credentials to access, but are unable to log into API Playground documentation, suggest contact you Refinitiv Account team to verify your assigned credentials.

Hello @krishna muppavarapu,

The information you are looking for is in most instances not specific to Elektron Websocket API, it it not originated with the API, rather it is conveyed from the infrastructure where it is generated to the consumer client application via API.

Depending on what infrastructure you are connecting to, this information on the errors can be best found in guides for that infrastructure,

For Elektron Realtine in cloud, some of this info is listed in ERT in Cloud Guide in section Error Responses.

For deployed TREP connections, the infra endpoint you are connecting to is ADS, and ADS Installation guide will list and explain the errors that originate with it in ADS Error Messages section.

The error message you are looking at is neither of these categories, it's a permission error, that means that user requesting TRI.N RIC is not permissioned to access TRI.N.

Should the user be perrmissioned for this instrument?

If not sure, it may be useful to ascertain what instruments the user is permissioned for, and it may be useful to to request delayed, non-fee-liable "\TRI.N" to test in the meantime.

Does this info help?

Hello @krishna muppavarapu,

RDP Pricing History service is documented via RDP API Playground (EAP)

Within Playground, filter History service, pick the sub-service "interday", and follow to Reference tab for the documentation.

There you will find RDP Pricing History errors, including the error that you are seeing.