KPI to be measured
Ask a question
Was this article helpful? 1 out of 1 found this helpful
The first thing to do when you are approaching THRON APIs is to obtain a valid session token which will allow you to perform web services requests. This has to be done by authenticating via an application that handles the integration.
Authenticate as an application providing appId
The second way to obtain a valid session token via THRON Custom Application Manager. This method is commonly used by developers who need to integrate with THRON ecosystem. At least one application must be installed, and the developer must know its appId and the appKey to perform authentication. If this is the case, in order to obtain a valid token you will have to invoke the loginApp web service which is included in the app package of xadmin. The URL of the request is structured as follows:
Where clientId is the domain name used to access THRON (usually your company name). Additional parameters (form params) to be included are:
Both these information can be found in the management screen of the THRON Custom Application Manager.
In the response you will find a tokenId which can be used to perform API requests. Its validity is set to 60 minutes, but each request performed with such token will "refresh" its validity.
Use an already active session's token
In some cases you might be provided with an already active session token (tokenId), which can be used to invoke web services. If this is your case, you just have to include the token as a request header in the form:
- X-TOKENID : yourTokenId
Once you are authenticated you will be able to perform via web services a series of actions related to the content the application (or the user) can see.
Most common actions are searches to retrieve specific content; in this article you will find a detailed explanation on how to perform searches. If you want to perform more accurate searches by leveraging additional information such as folders, tags or metadata, you might want to have a look at the following articles.
- Optimized content search exploiting folders
- Optimized content search exploiting tags
- Optimized content search exploiting key metadata
In some integration projects it might be necessary to perform requests through an application but still preserving the identity of the users; detailed instructions on how to do so are presented in this article.
Finally, before realizing your project, we recommend you read this article to inform yourself about the limitations imposed by the Platform.