All possible status codes

krishna muppavarapu

Is there any list of all possible status codes for Refinitiv Websocket API and History data platform API

For eg for Interday history we get below response. We need to know all possible status codes so that we can map these codes to our known exceptions.

[
{

"universe": {

"ric": "TRI.N"
},
"status": {

"code": "TS.Interday.UserNotPermission.70112",
"message": "User does not have permission for this universe."
}
}
]

zoya faberov

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.

zoya faberov

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?

krishna muppavarapu

zoya.farberov We connect to ERT in cloud using websocket api. I understand about the http response error codes from this API, but if the history http status is OK and response json has a status code. Then how do we know what are all status codes that can come from underlying api?

I just gave one example of user not permission status code but we need to know other possible status codes.

zoya faberov

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.

krishna muppavarapu

@zoya.farberov Thank you for your reply. I tried to use API playground but getting authentication failed. Please see the screenshot.

Please let me know how to get access to this content.