ApplicationId (256), and scope (trapi)
Hi
My question is first regarding the scope parameter which we send to get the authentication info about the access_token and refresh token. Is it compulsory to pass and is it ever going to be changed later from "trapi"?
Other question is regarding another parameter "Application ID" so combining here. Is the application Id going to be same for all users? Is it possible to change? and what does it represent actually if it is same for all?
Hi @bansalshah, You can read up on the scope here. Essentially, trapi is a root level scope and by specifying it, you are asking for an Access token, which can be used for any sub-scope API call. If for e.g. you get a token with sub scope like - trapi.data.esg.read, the app will not be able to invoke streaming prices API call with that token.
Practically, your application can use root level scope for everything. The app ID is something that you define and is for your own purposes only. It can be any 8 bit number and historically comes from DACS entitlement enforcement. Then, a user could check the ADS logs and see which APP ID is connected and such.
Hi .@Gurpreet. , Thank you so much for the response. I got the working of scope but talking about Application ID, it is called by varied different names like client id/ AppKey/ Application ID. What is the actual use of this and why are there different names for the same thing? If you check the above link you shared you will see the Client Id in the Table. Also if you check the ERT in cloud documentation it says to just put the Application Id as 256. So how are all this different from each other?
I am attaching links and snapshots of all articles.
Client ID is not the same as application ID that is used in websocket API. Client ID is defined by the user and registered with Refinitiv using the AppkeyGenerator in the online portal. It is used to warn and block the offending apps about the system usage and data limits.
Like I mentioned previously, Application ID, Position etc used in Websocket API is reminiscent of DACS parameters used with TREP system. Your app's application ID would be used in log messages into your local ADS. This is not the case with ERT Cloud and hence can be ignored.