Eikon Data API multiple session use different generate keys to run into the same PC

sunny.to@refinitiv.com

Hi team,

I got a questions from client which is relate to multiple applications to use different generate keys to run into the same PC by using Eikon Data API. Does it workn under Eikon desktop? if so, is it any impact or drawbacks?

AppKey.JPG

Regards,

Sunny

Alex Putkov.1

@sunny.to@refinitiv.com

To add to the response by @raksina.samasiri, Eikon API Proxy currently supports up to 10 multiple client sessions. In other words you can have up to 10 applications running simultaneously and retrieving data using Eikon Data APIs.
It is not necessary to use a separate app key for each application. You may use the same app key across all your applications or you could create a separate key for each app, whatever is more convenient for you. E.g. in case you'd like to run several instances of the same application at the same time, it would likely be more convenient to use the same app key and there's absolutely no need to use a separate app key for each instance of the same application.

raksina.samasiri

Hi @sunny.to@refinitiv.com,
The purpose of having multiple app keys is to identify that each session is called from which application. Hence, if the client is going to use the different generated keys on different applications and each app is doing a different thing, it's fine, and I don't think there's any limitation or drawbacks.

Also please note that the limit will be counted across all client applications connected to the same Eikon instance as mentioned in Eikon Data API Usage and Limits Guideline

Best regards,
Raksina

sunny.to@refinitiv.com

Thanks Alex. It is very useful information.

sunny.to@refinitiv.com

Thanks Raksina

sunny.to@refinitiv.com

Got it with thanks. Done.

sunny.to@refinitiv.com

According to Raksina,

Below use case that how client is going to use the different generated keys, is it because

1. Each app is doing the different thing so client want to identify which app is using each session
2. Each app is doing the same thing but client would like to reduce the execution time by running it in parallel
3. Each app is doing the same thing but client would like to get bypass the limit (API call, data size limit)
4. or any other case

Besides above use cases, If someone encountered other case, please add in below. Thanks.

Alex Putkov.1

@sunny.to@refinitiv.com

Only the first item on your list is a valid reason for utilizing multiple app keys.

1. Each app is doing the different thing so client want to identify which app is using each session
   Answer: This is the only valid reason I can think of for utilizing multiple app keys
2. Each app is doing the same thing but client would like to reduce the execution time by running it in parallel
   Answer: Utilizing multiple app keys will not help to reduce the runtime in any way. You just as well may use a single app key and run multiple instances of the same app or script or a number of different apps or scripts utilizing the same app key in parallel.
3. Each app is doing the same thing but client would like to get bypass the limit (API call, data size limit)
   Answer: Creating multiple app keys or running several instances of the same app, or multiple apps in parallel will not help to bypass any limits on data retrieval.
4. or any other case
   Answer: I cannot think of any use cases for utilizing multiple app keys, except #1 above.