This tutorial is an end-to-end walkthrough for setting up and running an instance of the SearchAssist Web SDK, which is a collection of libraries that you can use to integrate SearchAssist apps with your own web applications.


The following list describes the general steps you will take to install and configure the Web SDK.

  • Build an App to be integrated – To get started, you need to develop a search assist app through the SearchAssist business user portal, and then configure the app to run in the Web/Mobile Client channel. Refer here for how.
  • Create a new Credential – As a prerequisite, you need to create a credential that would be referred to while configuring the Web/Mobile client channel. Refer here for how.
  • Configure Web/Mobile Client channel – To use the SearchAssist app with the Web SDK, you must configure the App for the Web/Mobile Client channel using the credentials created in the above step. Refer here for how.
  • From the Web/Mobile client detail page and copy the below details from the Web/Mobile client details page
    • App Name
    • App ID
    • Client ID
    • Client secret ID
    • Search ID

Configuring web SDK

Now it is time to download, uncompress the file required for the Web SDK and a test application to run the SearchAssist App on your local host server.

  1. To download the SearchAssist Web SDK, go to, and then click Download.
  2. Extract all files to your local folder
  3. From the SearchAssist Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu, copy the following : (These values needs to updated in the ‘SearchAssist-config.js’ file)
    • App Name 
    • App ID
    • Client ID 
    • Client secret ID
    • Search ID
  4. Open the extracted folder, locate and navigate to /web-kore-sdk-private/findly/demo/ folder
  5. Open ‘SearchAssist-config.js’  file in any of the editors(Ex:- Notepad++, Visual studio)
  6. Update the botOptions parameters botInfo, clientId and clientSecret, and your email id as userIdentity.
    botOptionsFindly.koreAPIUrl = "Host URL"; (Ex: ‘’)
    botOptionsFindly.baseAPIServer = “”;   (Ex: ‘’)
    botOptionsFindly.botInfo = { chatBot: "", "taskBotId": ""};
    botOptionsFindly.clientId = "";
    botOptionsFindly.clientSecret = "";
    botOptionsFindly.searchIndexID = "";
    botOptionsFindly.reWriteSocketURL = {
            protocol: 'wss',
            hostname: ''  (Ex: ‘’)
  7. Save the changes done in the ‘SearchAssist-config.js’ file
  8. Locate and navigate to /web-kore-sdk-private/demo/ folder
  9. Right-click “index.html” file and open with any one of the browsers
  10. End User SDK will be opened with the changes done in the configured app
  11. Start the searches in the SDK and relevant results will be displayed.
  12. Data searched in the End User SDK (“searches”,”Users”,”Clicks” and “Appearance of Sources data”) will be displayed in the Business user portal.

Note: If the app is running in a local box, in order to validate it below steps are mandatory

  • We need to run SDK in chromium or chrome browser with security disability mode to allow the Cross-Origin Resource Sharing (CORS)  
  • For that open windows run command and paste chrome.exe –disable-web-security –user-data-dir=c:\my-chrome-data\data
  • Hit enter chrome will be opened in disabled security disabled mode paste the index.html path here to run the sdk

Passing data via webSDK

You can pass additional information of the user accessing the channel by adding the custom data at botInfo inside the SearchAssist-config.js file.

botOptionsFindly.botInfo = { chatBot: "<App Name>", 
                            "taskBotId": "<App ID>",
         } };


botOptionsFindly.botInfo = {chatBot: "<App Name>", 
                            "taskBotId": "<App ID>",

Commonly Encountered Errors

  • A wrong URL is given in index.html, users see a 404 error. Double-check the URL. URL changes depending on whether you are hosting the bot on your own web SDK or on SearchAssist’s web SDK.
  • Not found: User sees this error when either wrong clientID or no clientID is given. Check the correct ClientID from Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu
    botOptions.clientId = “{clientID}”; // secure client-id
  • error verifying the jwt: the Wrong clientSecret is given in index.html: Check the correct clientSecret you get from Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu
    “clientSecret”: "{clientSecret}” //provide clientSecret here

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed