API

While most developers will use the available SDK's or connectors to develop applications that interact with the Teneo Interaction Engine (or 'engine' in short), there may be a need to interact directly with the engine API, for example if no SDK is available for the platform you're working with. If that is the case, this is the page for you.

Engine URL

Once a solution has been developed and tested in Teneo Studio, it can be published to an engine. Once published, the engine contains the solution data and has a unique URL that client applications can use to interact with it.

You can find the engine url in the publication endpoint of your solution.

Requests

Requests to engine are sent over http(s). Both GET and POST requests are allowed, but POST requests are preferred. The Content-Type should be application/x-www-form-urlencoded.

Request parameters

Requests to engine usually contain the following main url parameters:

Parameter Description
userinput Optional. The natural language utterance of the user.
viewtype Required. Tells engine which jsp template to use for the error response. Use value tieapi.

In addition to the url parameters above, any other parameter can be included in the request. These can be used to provide additional information to your bot. A pre-processing script in your solution can be used to store them in a variable. More details on that here: Pre-processing.

Response

The engine response is returned in JSON and can consist of the following fields:

Key Description
status Always present. Status code. 0 = success, -1 = error, 1 = logout
input Optional. Map containing input details included in the request.
output Optional. Map containing engine output details.
message Optional. String containing message for responses with status other than 0.
sessionId Optional. String containing the engine sessionId. See Session Management.

Input object

Key Description
text String containing the input of the user as processed by engine.
parameters Map containing the additional parameters that were included in the request.

Output object

Key Description
text String containing the answer text of the output node.
emotion String containing the value of the emotion field of the output node.
link String containing the output hyperlink field of the output node.
parameters Map containing the output node's output parameters.

Example

Example of a request that contains the following parameters:

Parameter Value
userinput What time is it?
usertimezone CEST
viewtype tieapi

Request

curl -X POST \
  https://developerarea-dev.teneocloud.com/tiesdktest/ \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'userinput=What%20time%20is%20it%3F&usertimezone=CEST&viewtype=tieapi'

Response

{
    "status": 0,
    "input": {
        "text": "What time is it?",
        "parameters": {
            "usertimezone": "CEST"
        }
    },
    "output": {
        "text": "Good afternoon! It's 15:26.",
        "emotion": "happy",
        "link": "https://example.com",
        "parameters": {
        }
    },
    "sessionId": "31992FA776A35DABA3291A4EE1031B5F"
}

Error response

{
    "status": -1,
    "input": {
        "text": "What time is it?",
        "parameters": {
            "usertimezone": "CEST"
        }
    },
    "message": "Teneo backend error",
    "sessionId": "31992FA776A35DABA3291A4EE1031B5F"
}

Session Management

To allow engine to remember details between requests, client applications should maintain a session with engine. The engine handles sessions as follows:

  1. When a request comes in that does not contain session details, a new session will be created on the server. The session ID is included in the JSON response and as a cookie in the response header.
  2. To maintain a dialog in the same session, the next request of the client should include the session ID received in the response.
  3. After 10 minutes of inactivity, engine will expire the session. All details stored in the session will be forgotten.
  4. If a request comes in with a session ID that is expired or unknown, engine will create a new empty session and include the new session ID in the response.

When using the SDK's, session maintenance is usually not something you have to worry about, as it is handled by the SDK. If you don't make use of the SDK's, you should make sure the session cookie received from engine is included in the request header. The way to do this depends on the language used. In node.js for example, this could be achieved as follows:

https.get({
      host: 'developerarea-dev.teneocloud.com',
      path: 'tiesdktest/?viewtype=tieapi&userinput=What%20time%20is%20it%3F&usertimezone=CEST',
      method: 'POST',
      headers: {
          'Cookie': 'JSESSIONID=31992FA776A35DABA3291A4EE1031B5F'
      }
}, function(response) {
        // handle response
});

Ending a session

Usually you don't have to explicitly end a session, engine will automatically expire a session after 10 minutes of inactivity (this timeout is configurable). However, you can force engine to end a session by appending 'endsession' to the engine url. Make sure the session cookie is included in the request, otherwise engine won't know which session to end.

Example request

curl -X POST \
  https://developerarea-dev.teneocloud.com/tiesdktest/endsession \
  -H 'Content-Type: application/x-www-form-urlencoded'

Example response

{
    "status" : 1,
    "message" : "logout"
}

Cross-Origin Resource Sharing (CORS)

When interacting with the Teneo Engine using javascript in a browser, the domain that is making requests is often different from the domain used by the Teneo Engine. Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to tell a browser to let a web application running at one origin (domain) have permission to access selected resources from a server at a different origin.

By default the Teneo Engine includes CORS headers in the responses to browser requests coming from any domain. This means any site can interact with a Teneo Engine. If you want to restrict your solution to only include CORS headers for specific domains, you can add a file called tieapi_cors_origins.txt to your solution. In Teneo Studio, use the Teneo Resource File Manager to add the file to the views folder. The file should contain the list of allowed origin domains (one domain per line, domains should include port numbers if applicable).

Was this page helpful?