IBM Embedded Business AI Framework




Web integration

It is possible to integrate EBA directly into your own web application as an embedded window. You can view an example.

There are two simple steps required to perform this integration:

  1. Add a script tag that initializes a global IBM_EBA interface object
  2. Calling the api exposed by the IBM_EBA object

Adding IBM_EBA and Calling Setup

This script should be loaded in the start of your application by simply adding a script tag which points to the path of the script. After loading this script, you should execute IBM_EBA.setup to pass any relevant data and credentials for logging into a session with EBA. Note, in the example below, we have added an additional script tag in the beginning of the file to illustrate a method for providing custom initialization.

    <title>Host Application</title>
        IBM_EBA_CONFIG = {
            access_token: '...',
            agent_name: 'Agent Kevin',
            disable_button: false,
            disable_shadow: true,
            loading_delay: 1000,
            user_first_name: 'John',
            user_last_name: 'Doe',
            user_full_name: 'John M. Doe',
            user_locale: 'en_US',
            user_language: 'en',
            user_time_zone: 'America/Los_Angeles'
    <script src="" defer></script>

With these few lines of code in your host application, EBA will be up and running.

As mentioned above, you can pass in the following fields to customize EBA either via optional global object IBM_EBA_CONFIG or during the call to IBM_EBA.setup, viz.

In order to create a new session for authorized user you will need to supply a JWT signed access_token. An access_token should be generated based on the iss, sub, and private key provided within our Lab Settings, where we have outlined the required integration steps. For an example on generating this access_token programmatically, please reference our headless integration.

For information on how to enable a multi-user integration so that all targeted end users within a host application may access a designated EBA environment, consult our multi-user integration paths


Since IBM_EBA is a global object, you will be able to send data to the assistant any time you like by simply invoking IBM_EBA.send. This enables you to encode various events across your web application. For instance, here is a click event that triggers an order event inside of EBA:

function onViewOrder() {
        order_meta: {
            order_id: 1234,
            order_name: 'paper',
            customer_id: 5678
<button onclick="onViewOrder()">View Order</button>

Using our development lab, you will be able to program the assistant to appropriately respond to this event. You may invoke the other api functions across your event handlers in a similar fashion. For details on how to respond to such events using EBA, please refer to our @react endpoint.

Display Modes

EBA supports four display modes which reflect the size of the embedded iframe:

Note: compact mode is designed to only show the content of the last message and serves as a popup. The show/hide semantics for compact mode is as follows: if the iframe is in a hidden state and the most recent message is tagged as important, then the popup will be shown. Otherwise, it will be hidden. Hence compact is designed to give the assistant a way to show itself on screen while it is hidden.

edit this article