Forbidden 403 error

manoj.pandeti

Hello,

I'm using the machine id and password with client id but I'm having a forbidden 403 error after authentication. Could you please guide me?

Sending EDP-GW service discovery request to https://api.refinitiv.com/streaming/pricing/v1/

EDP-GW service discovery HTTP code: 403 Forbidden

Stop trying with the request

Failed to retrieve endpoints from EDP Service Discovery. Exiting...

Machine ID : GE-A-01444311-3-2480

nawapoom.lohajarernvanich

This response is coming from the machine ID that has expired license. Therefore, it can get the access token but failed to retrieve service directory with 403 error message. I can reproduce the same error with my testing ID.

Once the new trial license is in place, you should be able to start to retrieve the data with the same credentials.

manoj.pandeti

If the problem is because of the host, please suggest me how to find the host name.

Thanks.

pimchaya.wongrukun01

Hello @monojit.banerjee

Have you got access token successfully? If yes, please see the answers in this question which may help you.

wasin.w

Hello @monojit.banerjee

If you got the access token successfully, could you please check if the returns JSON message from RDP authentication has "trapi.streaming.pricing.read" value in the scope attribute?

Basically, the Service Discovery ("/pricing/v1") requires trapi.streaming.pricing.read permission scope to access the list of ERT Cloud VIPs.

wasin.w

@monojit.banerjee

Could you please share your "scope" value from the JSON access token?

nawapoom.lohajarernvanich

Hi @manoj.pandeti

This is not about the hostname but the previous trial has been expired. I have reached out to the account team and they have activated the 30-day trial period for this machine ID.

manoj.pandeti

Thanks I could able to connect now. But, I'm getting static data after that it couldn't able to get Live Stream data. Is that the expected behaviour? Please help me with that.

Sending authentication request with password to https://api.refinitiv.com:443/auth/oauth2/beta1/token ...

EDP-GW Authentication succeeded. RECEIVED:

{

"access_token":"eyJ0e.....FPHjpg",

"expires_in":"300",

"refresh_token":"9c...-...-b8",

"scope":"trapi.streaming.pricing.read",

"token_type":"Bearer"

}

Sending EDP-GW service discovery request to https://api.refinitiv.com/streaming/pricing/v1/

EDP-GW Service discovery succeeded. RECEIVED:

{

"services":[

{

"dataFormat":[

"tr_json2"

],

"endpoint":"amer-2.pricing.streaming.edp.thomsonreuters.com",

"location":[

"us-east-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"amer-3.pricing.streaming.edp.thomsonreuters.com",

"location":[

"us-east-1a",

"us-east-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"apac-2.pricing.streaming.edp.thomsonreuters.com",

"location":[

"ap-southeast-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"emea-1.pricing.streaming.edp.thomsonreuters.com",

"location":[

"eu-west-1a"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"apac-3.pricing.streaming.edp.thomsonreuters.com",

"location":[

"ap-southeast-1a",

"ap-southeast-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"emea-2.pricing.streaming.edp.thomsonreuters.com",

"location":[

"eu-west-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"emea-3.pricing.streaming.edp.thomsonreuters.com",

"location":[

"eu-west-1a",

"eu-west-1b"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"apac-1.pricing.streaming.edp.thomsonreuters.com",

"location":[

"ap-southeast-1a"

],

"port":443,

"provider":"aws",

"transport":"websocket"

},

{

"dataFormat":[

"tr_json2"

],

"endpoint":"amer-1.pricing.streaming.edp.thomsonreuters.com",

"location":[

"us-east-1a"

],

"port":443,

"provider":"aws",

"transport":"websocket"

}

]

}

Connecting to WebSocket wss://amer-3.pricing.streaming.edp.thomsonreuters.com:443/WebSocket for session1...

WebSocket successfully connected for session1!

SENT on session1:

{

"Domain":"Login",

"ID":1,

"Key":{

"Elements":{

"ApplicationId":"256",

"AuthenticationToken":"ey...Hjpg",

"Position":"192.168.2.75/Operations-PC"

},

"NameType":"AuthnToken"

}

}

RECEIVED on session1:

RECEIVED on session1:

WebSocket Closed for session1

Reconnect to the endpoint for session1 after 3 seconds...

Connecting to WebSocket wss://amer-3.pricing.streaming.edp.thomsonreuters.com:443/WebSocket for session1...

WebSocket successfully connected for session1!

SENT on session1:

{

"Domain":"Login",

"ID":1,

"Key":{

"Elements":{

"ApplicationId":"256",

"AuthenticationToken":"eyJ0eX...jpg",

"Position":"192.168.2.75/Operations-PC"

},

"NameType":"AuthnToken"

}

}

RECEIVED on session1:

Can you please help with this

wasin.w

Hello @manoj.pandeti

I cannot find an item request message in a given JSON log. Does the application request any items to ERT in Cloud yet?

You can find more detail regarding how to connect and consume data from ERT in cloud via the following resources:

• Elektron WebSocket API Tutorial: Request Data from Server
• Elektron WebSocket API Quick Start:
• Elektron WebSocket API examples for ERT in Cloud

wasin.w

Hello @manoj.pandeti

Do you still encounter any connection and subscription problems?