The frequency of the stream response using the Electron Web Socket API is not as expected.

The frequency of the stream response using the Electron Web Socket API is not as expected.

We expected near realtime update messages when using Web Socket API for single FX RIC = GBP=X

But the update messages are minuets apart.

We are using the Python sample application from the Elektron docs. See the following command

python market_price_edpgw_service_discovery.py --user GE-A-01652483-3-2337 --password OURPASSWORD --clientid OURCLIENTID --ric GBP=X

Please advise how we get more frequent updates using the WebSocket API.

Find more posts tagged with

trep

websockets

rrto

elektron-sdk

rdp-api

Accepted answers

Tim Smith

GBP=X is a snapshot update for Sterling against US Dollar. It is on the realtime network but it wont update as a stream only every ten minutes. If you want a streaming update then the RIC is GBP= (although you may not have access to this RIC as it requires an extra level of permissioning).

All comments

Tim Smith

You could also use GBP=S which is a two minute snapshot RIC.

umer.nalla

Hi @Laarni Evelyn Acierto.Santiago

This is related to the choice of RIC rather than the API.

For example, if I request GBP=X using any realtime API such as RFA /EMA etc it also does not update that often.

If, however, I request GBP= using the same APIs, then it updates far more frequently.

I am not a content expert so cannot tell you the difference between GBP= and GBP=X and why they update at different rates. Please ask the content helpdesk for the difference.

Elektron Websocket API from Elektron Realtime in Cloud currently delivers 3 updates a second (assuming any Market Activity actually takes place) + plus all trades as well - this is known as Trade Safe conflation.

I am getting updates one minute apart even for the `/GBP=`.

EXPLORE OUR SITES