The XO Platform allows you to develop Virtual Assistants using secured APIs. All key developer activities like creation, import and export, training, and publishing are available using these APIs. Key account management activities like managing XO Platform access, managing admin, and roles can also be performed via secured public APIs. For a complete list of APIs and usage instructions, refer here.

Authentication of the API requests involves the following two steps:

1. Create an App: An App helps you create secure authentication credentials to access the XO Platform features. You can associate the app for enabling BotKit, APIs, SDKs, and Channels.
2. Assign API Scopes to an App: Assigning API scopes to the app allows the app to access the Platform APIs securely:
   • XO Platform API Scopes: Developers can assign appropriate API Scopes to the app to access respective Platform features for a virtual assistant.
   • Bot Admin Console API Scopes: Account administrators can assign API Scopes to the app to access respective features in any virtual assistants built into their accounts on the Platform.

Creating and Managing Apps in XO Platform

Steps to create a Client App from the XO Platform:

1. Go to Deploy > APIs & Extensions > Manage Apps.
   
2. If you are creating an app for the first-time, click the Create App button. Otherwise, click the New App button.
3. On the Create Client App page, enter a name for the app.
4. Select Enforce JTI, JWE, or both as per your requirements to secure the connections with the Platform:
   • Enforce JTI (JWT ID) Claim – Once enabled, the Platform accepts the requests only from calls with the JTI Claim in the requests and those without JTI Claim are rejected.
   • Enforce JWE Encryption (Generating JWT token) – To access the XO Platform’s public APIs, the application making the API request requires authentication. Kore.ai uses the JWT (JSON Web Token) mechanism to handle the authentication. For a quick overview of the JWT token, read Introduction to JWT tokens.
     
5. Click Next and Done.
   You are directed to the Manage Apps page, which lists all the apps associated with this virtual assistant. 
6. Click the app name or anywhere in the row to see the app’s details, such as Bot Name, Bot ID, Client ID, and Client Secret. Also, the App Usage column lists where this app is used – Web SDK, BotKit, APIs, WebHook and IVR Channels.
   Note: Use the Client ID and Client Secret of the client app from above to generate a JWT token. This token must be passed as a part of each API request for authorization.
7. To delete apps, click the Delete icon against the respective app.
   Note: Only the Bot Owner can delete an app.

Creating and Managing Apps in Bots Admin Console

Steps to create a Client App from the Bot Admin Console:

1. Log in to the Admin Console.
2. Go to Security & Control > API Scopes.
3. On the API Scopes page, click New.
4. Click the Manage Apps link to create a new app.
   
5. Click New App and then do the following:
   • Enter a name.
   • Select Enforce JTI, JWE, or both as per your requirements.
6. Click Save.

Data Tables

Access control from the Data Tables module is different from the XO Platform and Bot Admin Console access controls.

You can define apps to securely access the data from data tables and data views.

• You can create one or more apps, Learn more.
• These apps can be used for:
  • Accessing the data tables and views over public APIs.
  • Accessing the data tables and views using Service Node.
  • Accessing the export and import API for the definition of data table and views.
• You can grant this app read, write, and delete permissions to each table and view separately, Learn more.

Associating API Scopes

Once you create a client app, you can associate it with API scopes.

Adding API Scopes in the XO Platform

Steps to associate API Scopes to a Client App from the XO Platform:

1. Go to Deploy > API & EXTENSIONs > API Scopes and click Create API Scope.
   
2. On the New API Scope Mapping page, from the App drop-down list, select an existing client app for authentication.
3. The app’s Client ID and Client Secret are displayed on the screen. Copy these values.
   
   
4. Under the Scopes section, select the appropriate scopes to allow the client app to access the respective APIs. (If appropriate scopes are not selected, then the client apps cannot access the APIs).
5. Click Save.

Adding API Scopes in the Bots Admin Console

Steps to associate API Scopes to a Client App from the Bot Admin Console:

1. Log in to the Admin Console.
2. Go to Security & Control > API Scopes.
3. On the API Scopes page, click New.
4. On the New API Scope Mapping page, from the App drop-down list, select an existing client app for authentication.
5. Click the Manage Apps link to create a new app.
6. Once you select an app, the Client ID and Client Secret appear. Copy these values.
7. Under the Scopes section, select the appropriate Scopes to allow the client app to access the respective APIs.Learn more.
8. Click Save. The app and associated scopes are listed on the API Scopes page.
   
9. If you want to delete an app and its associated API Scope, click the Delete icon against the respective app.

List of Available API Scopes

Generating the JWT Token

Once you have associated the API scopes with a client app, you must generate the JWT token for API requests.

Steps to generate the token:

1. Visit https://developer.kore.ai/v10-1/tools/jwt/.
2. In the Algorithm drop-down list, select HS256.
3. Scroll down to the Decoded section, and update the Playload and the Secret.
   1. 1. Replace the content of the Payload field with the code block shown below, and add the Client ID of the app copied in the previous section.
         {
"sub": "1234567890",
"appId": "add-Client-ID-here"
}
   Note: The XO Platform validates the token only when it is entered exactly as “appId”. Don’t use “App ID”, “appid”, or “app ID”.
4. In the Verify Signature field, replace your-256-bit-secret with the Client Secret copied in the previous section.

• Click Copy JWT to copy the generated token. You can pass this token as a part of the API request for authorization.