IBM Cloud API Docs
Tone Analyzer

Introduction

The IBM Watson™ Tone Analyzer service uses linguistic analysis to detect emotional and language tones in written text. The service can analyze tone at both the document and sentence levels. You can use the service to understand how your written communications are perceived and then to improve the tone of your communications. Businesses can use the service to learn the tone of their customers' communications and to respond to each customer appropriately, or to understand and improve their customer conversations.

Note: Request logging is disabled for the Tone Analyzer service. Regardless of whether you set the X-Watson-Learning-Opt-Out request header, the service does not log or retain data from requests and responses.

Beginning with version 4.0.0, the Node SDK returns a Promise for all methods when a callback is not specified.

The package location moved to ibm-watson. It remains available at watson-developer-cloud but is not updated there. Use ibm-watson to stay up to date.

The IBM Watson Unity SDK has the following requirements.

  • The SDK requires Unity version 2018.2 or later to support TLS 1.2.
    • Set the project settings for both the Scripting Runtime Version and the Api Compatibility Level to .NET 4.x Equivalent.
    • For more information, see TLS 1.0 support.
  • The SDK does not support the WebGL projects. Change your build settings to any platform except WebGL.

For information about how to install and configure the SDK and SDK Core, see https://github.com/watson-developer-cloud/unity-sdk.

The code examples on this tab use the client library that is provided for Java.

Maven

<dependency>
  <groupId>com.ibm.watson</groupId>
  <artifactId>ibm-watson</artifactId>
  <version>7.3.0</version>
</dependency>

Gradle

compile 'com.ibm.watson:ibm-watson:7.3.0'

GitHub

https://github.com/watson-developer-cloud/java-sdk

The code examples on this tab use the client library that is provided for Node.js.

Installation

npm install ibm-watson

GitHub

https://github.com/watson-developer-cloud/node-sdk

The code examples on this tab use the client library that is provided for Python.

Installation

pip install --upgrade "ibm-watson>=3.2.0"

GitHub

https://github.com/watson-developer-cloud/python-sdk

The code examples on this tab use the client library that is provided for Ruby.

Installation

gem install ibm_watson

GitHub

https://github.com/watson-developer-cloud/ruby-sdk

The code examples on this tab use the client library that is provided for Go.

go get -u github.com/watson-developer-cloud/go-sdk/...

GitHub

https://github.com/watson-developer-cloud/go-sdk

The code examples on this tab use the client library that is provided for Swift.

Cocoapods

pod 'IBMWatsonToneAnalyzerV3', '~> 2.2.0'

Carthage

github "watson-developer-cloud/swift-sdk" ~> 2.2.0

Swift Package Manager

.package(url: "https://github.com/watson-developer-cloud/swift-sdk", from: "2.2.0")

GitHub

https://github.com/watson-developer-cloud/swift-sdk

The code examples on this tab use the client library that is provided for .NET Standard.

Package Manager

Install-Package IBM.Watson.ToneAnalyzer.v3 -Version 3.3.0

.NET CLI

dotnet add package IBM.Watson.ToneAnalyzer.v3 -version 3.3.0

PackageReference

<PackageReference Include="IBM.Watson.ToneAnalyzer.v3" Version="3.3.0" />

GitHub

https://github.com/watson-developer-cloud/dotnet-standard-sdk

The code examples on this tab use the client library that is provided for Unity.

Github

https://github.com/watson-developer-cloud/unity-sdk

https://github.com/IBM/unity-sdk-core

Authentication

IBM Cloud is migrating to token-based Identity and Access Management (IAM) authentication.

  • With some service instances, you authenticate to the API by using IAM. You can pass either a bearer token in an Authorization header or an API key. Tokens support authenticated requests without embedding service credentials in every call. API keys use basic authentication. Learn more about IAM.

    If you pass in an API key, use apikey for the username and the value of the API key as the password.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

    If you pass in the value of the API key, the SDK manages the lifecycle of the tokens. If you pass a token, you maintain the token lifecycle. Learn more about IAM authentication with the SDK.

  • In other instances, you authenticate by providing the username and password for the service instance. For more information, see Service credentials for Watson services.

To find out which authentication to use, view the service credentials by clicking the service instance in the Resource list.

The "username" and "password" in the service credentials are different from your IBM Cloud account IBMid and password.

IAM authentication. Replace {apikey} and {url} with your service credentials.

curl -u "apikey:{apikey}" -X {request_method} "{url}/{method}"

Basic authentication. Replace {username}, {password}, and {url} with your service credentials.

curl -u "{username}:{password}" -X {request_method} "{url}/{method}"

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

IamOptions options = new IamOptions.Builder()
    .apiKey("{apikey}")
    .build();
ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", options);
toneAnalyzer.setEndPoint("{url}");

Basic authentication. Replace {username}, {password}, {version}, and {url}. Use either of the two constructors.

ToneAnalyzer toneAnalyzer = new ToneAnalyzer(
    "{version}",
    "{username}",
    "{password}");
toneAnalyzer.setEndPoint("{url}");

or

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}");
toneAnalyzer.setUsernameAndPassword("{username}","{password}");
toneAnalyzer.setEndPoint("{url}");

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

const ToneAnalyzerV3 = require('ibm-watson/tone-analyzer/v3');

const toneAnalyzer = new ToneAnalyzerV3({
  version: '{version}',
  iam_apikey: '{apikey}',
  url: '{url}'
});

Basic authentication. Replace {username}, {password}, {version}, and {url}.

const  = require('ibm-watson/tone-analyzer/v3');

const toneAnalyzer = new ToneAnalyzerV3({
  version: '{version}',
  username: '{username}',
  password: '{password}',
  url: '{url}'
});

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

from ibm_watson import ToneAnalyzerV3

tone_analyzer = ToneAnalyzerV3(
    version='{version}',
    iam_apikey='{apikey}',
    url='{url}'
)

Basic authentication. Replace {username}, {password}, {version}, and {url}.

from ibm_watson import ToneAnalyzerV3

tone_analyzer = ToneAnalyzerV3(
    version='{version}',
    username='{username}',
    password='{password}',
    url='{url}'
)

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

require "ibm_watson"

tone_analyzer = IBMWatson::ToneAnalyzerV3.new(
  version: "{version}",
  iam_apikey: "{apikey}",
  url:"{url}"
)

Basic authentication. Replace {username}, {password}, {version}, and {url}.

require "ibm_watson"

tone_analyzer = IBMWatson::ToneAnalyzerV3.new(
  version: "{version}",
  username: "{username}",
  password: "{password}",
  url:"{url}"
)

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

import "github.com/watson-developer-cloud/go-sdk/toneanalyzerv3"

toneAnalyzer, toneAnalyzerErr := toneanalyzerv3.NewToneAnalyzerV3(&toneanalyzerv3.ToneAnalyzerV3Options{
  Version: "{version}",
  IAMApiKey: "{apikey}",
  URL: "{url}",
})

Basic authentication. Replace {username}, {password}, {version}, and {url}.

import "github.com/watson-developer-cloud/go-sdk/toneanalyzerv3"

toneAnalyzer, toneAnalyzerErr := toneanalyzerv3.NewToneAnalyzerV3(&toneanalyzerv3.ToneAnalyzerV3Options{
  Version: "{version}",
  Username: "{username}",
  Password: "{password}",
  URL: "{url}",
})

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

let toneAnalyzer = ToneAnalyzer(version: "{version}", apiKey: "{apikey}")

toneAnalyzer.serviceURL = "{url}"

Basic authentication. Replace {username}, {password}, {version}, and {url}.

let toneAnalyzer = ToneAnalyzer(version: "{version}", username: "{username}", password: "{password}")

toneAnalyzer.serviceURL = "{url}"

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

IamConfig config = new IamConfig(
    apikey: "{apikey}"
    );

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", config);
toneAnalyzer.SetEndpoint("{url}");

Basic authentication. Replace {username}, {password}, {version}, and {url}.

BasicAuthConfig config = new BasicauthConfig(
    username: "{username}",
    password: "{password}"
);

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", config);
toneAnalyzer.SetEndpoint("{url}");

SDK managing the IAM token. Replace {apikey}, {version} and {url}.

IamTokenOptions tokenOptions = new IamTokenOptions()
{
    IamApiKey = "{apikey}"
};
Credentials credentials = new Credentials(tokenOptions);
while (!credentials.HasTokenData())
{
    yield return null;
}

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "{url}";

Basic authentication. Replace {username}, {password}, {version}, and {url}.

Credentials credentials = new Credentials("{username}", "{password}");

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "{url}";

Service endpoint

The service endpoint is based on the location of the service instance. For example, when Tone Analyzer is hosted in Frankfurt, the base URL is https://gateway-fra.watsonplatform.net/tone-analyzer/api. The URL might also be different when you use IBM Cloud Dedicated.

To find out which URL to use, view the service credentials by clicking the service instance in the Resource list.

Use that URL in your requests to Tone Analyzer.

Set the correct service URL by calling the setEndPoint() method of the service instance.

Set the correct service URL by calling the url parameter when you create the service instance.

Set the correct service URL by calling the url parameter when you create the service instance or by calling the set_url() method of the service instance.

Set the correct service URL by calling the url parameter when you create the service instance or by calling the url= method of the service instance.

Set the correct service URL by the URL parameter when you create the service instance or by calling the SetURL= method of the service instance.

Set the correct service URL by setting the serviceURL property of the service instance.

Set the correct service URL by calling the SetEndpoint() method of the service instance.

Set the correct service URL by setting the Url property of the service instance.

Service endpoints by location:

  • Dallas: https://gateway.watsonplatform.net/tone-analyzer/api
  • Washington DC: https://gateway-wdc.watsonplatform.net/tone-analyzer/api
  • Frankfurt: https://gateway-fra.watsonplatform.net/tone-analyzer/api
  • Sydney: https://gateway-syd.watsonplatform.net/tone-analyzer/api
  • Tokyo: https://gateway-tok.watsonplatform.net/tone-analyzer/api
  • London: https://gateway-lon.watsonplatform.net/tone-analyzer/api

All locations might not support Tone Analyzer. For details, see Service availability.

Dallas API endpoint example

curl -u "apikey:{apikey}" -X {request_method} "https://gateway.watsonplatform.net/tone-analyzer/api"

Your service instance might not use this URL

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Example for the Washington DC location

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}");
toneAnalyzer.setEndPoint("https://gateway-wdc.watsonplatform.net/tone-analyzer/api");

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Example for the Washington DC location

const ToneAnalyzerV3 = require('ibm-watson/tone-analyzer/v3');

const toneAnalyzer = new ToneAnalyzerV3({
  version: '{version}',
  iam_apikey: '{apikey}',
  url: 'https://gateway-wdc.watsonplatform.net/tone-analyzer/api'
});

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Examples for the Washington DC location in the constructor and after instantiation

tone_analyzer = ToneAnalyzerV3(
    version='{version}',
    iam_apikey='{apikey}',
    url='https://gateway-wdc.watsonplatform.net/tone-analyzer/api'
)

or

tone_analyzer.set_url('https://gateway-wdc.watsonplatform.net/tone-analyzer/api')

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Examples for the Washington DC location in the constructor and after instantiation

tone_analyzer = IBMWatson::.new(
  version: "{version}",
  api_key: "{apikey}",
  url: "https://gateway-wdc.watsonplatform.net/tone-analyzer/api"
)

or

tone_analyzer.url = "https://gateway-wdc.watsonplatform.net/tone-analyzer/api"

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Examples for the Washington DC location in the constructor and after instantiation

toneAnalyzer, toneAnalyzerErr := toneanalyzerv3.NewToneAnalyzerV3(&toneanalyzerv3.ToneAnalyzerV3Options{
  Version: "{version}",
  IAMApiKey: "{apikey}",
  URL: "https://gateway-wdc.watsonplatform.net/tone-analyzer/api",
})

or

toneAnalyzer.SetURL("https://gateway-wdc.watsonplatform.net/tone-analyzer/api")

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Example for the Washington DC location

let toneAnalyzer = ToneAnalyzer(version: "{version}", apiKey: "{apikey}")
toneAnalyzer.serviceURL = "https://gateway-wdc.watsonplatform.net/tone-analyzer/api"

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Example for the Washington DC location

IamConfig config = new IamConfig(
    apikey: "{apikey}"
    );

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", config);
toneAnalyzer.SetEndpoint("https://gateway-wdc.watsonplatform.net/tone-analyzer/api");

Default URL

https://gateway.watsonplatform.net/tone-analyzer/api

Example for the Washington DC location

IamTokenOptions tokenOptions = new IamTokenOptions()
{
    IamApiKey = "{apikey}"
};
Credentials credentials = new Credentials(tokenOptions);
while (!credentials.HasTokenData())
{
    yield return null;
}

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "https://gateway-wdc.watsonplatform.net/tone-analyzer/api";

Disabling SSL verification

All Watson services use Secure Sockets Layer (SSL) (or Transport Layer Security (TLS)) for secure connections between the client and server. The connection is verified against the local certificate store to ensure authentication, integrity, and confidentiality.

If you use a self-signed certificate, you need to disable SSL verification to make a successful connection.

Enabling SSL verification is highly recommended. Disabling SSL jeopardizes the security of the connection and data. Disable SSL only if absolutely necessary, and take steps to enable SSL as soon as possible.

To disable SSL verification for a curl request, use the --insecure (-k) option with the request.

To disable SSL verification, create an HttpConfigOptions object and set the disableSslVerification property to true. Then pass the object to the service instance by using the configureClient method.

To disable SSL verification, set the disable_ssl_verification parameter to true when you create the service instance.

To disable SSL verification, call the disable_SSL_verification method on the service instance.

To disable SSL verification, call the configure_http_client method on the service instance and set the disable_ssl parameter to true.

To disable SSL verification, call the DisableSSLVerification method on the service instance.

To disable SSL verification, call the disableSSLVerification() method on the service instance. You cannot disable SSL verification on Linux.

To disable SSL verification, set the DisableSslVerification method to true on the service instance.

To disable SSL verification, call the DisableSslVerification method on the service instance.

Example that disables SSL verification

IAM authentication. Replace {apikey} and {url} with your service credentials.

curl -k -u "apikey:{apikey}" -X {request_method} "{url}/{method}"

Example that disables SSL verification

IamOptions options = new IamOptions.Builder()
    .apiKey("{apikey}")
    .build();
ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", options);
toneAnalyzer.setEndPoint("{url}");

HttpConfigOptions configOptions = new HttpConfigOptions.Builder()
  .disableSslVerification(true)
  .build();
toneAnalyzer.configureClient(configOptions);

Example that disables SSL verification

const ToneAnalyzerV3 = require('ibm-watson/tone-analyzer/v3');

const toneAnalyzer = new ToneAnalyzerV3({
  version: '{version}',
  iam_apikey: '{apikey}',
  url: '{url}',
  disable_ssl_verification: true,
});

Example that disables SSL verification

from ibm_watson import ToneAnalyzerV3

tone_analyzer = ToneAnalyzerV3(
    version='{version}',
    iam_apikey='{apikey}',
    url='{url}'
)
tone_analyzer.disable_SSL_verification()

Example that disables SSL verification

require "ibm_watson"

tone_analyzer = IBMWatson::ToneAnalyzerV3.new(
  version: "{version}",
  iam_apikey: "{apikey}",
  url:"{url}"
)
tone_analyzer.configure_http_client(disable_ssl: true)

Example that disables SSL verification

import "github.com/watson-developer-cloud/go-sdk/toneanalyzerv3"

toneAnalyzer, toneAnalyzerErr := toneanalyzerv3.NewToneAnalyzerV3(&toneanalyzerv3.ToneAnalyzerV3Options{
  Version: "{version}",
  IAMApiKey: "{apikey}",
  URL: "{url}",
})
toneAnalyzer.DisableSSLVerification()

Example that disables SSL verification


let toneAnalyzer = ToneAnalyzer(version: "{version}", apiKey: "{apikey}")
toneAnalyzer.disableSSLVerification()

Example that disables SSL verification

IamConfig config = new IamConfig(
    apikey: "{apikey}"
    );

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", config);
toneAnalyzer.SetEndpoint("{url}");
toneAnalyzer.DisableSslVerification(true);

Example that disables SSL verification

IamTokenOptions tokenOptions = new IamTokenOptions()
{
    IamApiKey = "{apikey}"
};
Credentials credentials = new Credentials(tokenOptions);
while (!credentials.HasTokenData())
{
    yield return null;
}

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "{url}";

toneAnalyzer.DisableSslVerification = true;

Versioning

API requests require a version parameter that takes a date in the format version=YYYY-MM-DD. When we change the API in a backwards-incompatible way, we release a new version date.

Send the version parameter with every API request. The service uses the API version for the date you specify, or the most recent version before that date. Don't default to the current date. Instead, specify a date that matches a version that is compatible with your app, and don't change it until your app is ready for a later version.

Specify the version to use on API requests with the version parameter when you create the service instance. The service uses the API version for the date you specify, or the most recent version before that date. Don't default to the current date. Instead, specify a date that matches a version that is compatible with your app, and don't change it until your app is ready for a later version.

This documentation describes the current version of Tone Analyzer, 2017-09-21. In some cases, differences in earlier versions are noted in the descriptions of parameters and response models.

Error handling

The Tone Analyzer service uses standard HTTP response codes to indicate whether a method completed successfully. HTTP response codes in the 2xx range indicate success. A response in the 4xx range is some sort of failure, and a response in the 5xx range usually indicates an internal system error that cannot be resolved by the user. Response codes are listed with the method.

ErrorResponse

Name Description
code
integer		 The HTTP response code.
sub_code
string		 A service-specific error code.
error
string		 General description of an error.
help
string		 A URL to documentation explaining the cause and possibly solutions for the error.

The Java SDK generates an exception for any unsuccessful method invocation. All methods that accept an argument can also throw an IllegalArgumentException.

Exception Description
IllegalArgumentException An illegal argument was passed to the method.

When the Java SDK receives an error response from the Tone Analyzer service, it generates an exception from the com.ibm.watson.developer_cloud.service.exception package. All service exceptions contain the following fields.

Field Description
statusCode The HTTP response code that is returned.
message A message that describes the error.

When the Node SDK receives an error response from the Tone Analyzer service, it creates an Error object with information that describes the error that occurred. This error object is passed as the first parameter to the callback function for the method. The contents of the error object are as shown in the following table.

Error

Field Description
code The HTTP response code that is returned.
message A message that describes the error.

The Python SDK generates an exception for any unsuccessful method invocation. When the Python SDK receives an error response from the Tone Analyzer service, it generates an ApiException that contains the following fields.

Field Description
code The HTTP response code that is returned.
message A message that describes the error.
info A dictionary of additional information about the error.

When the Ruby SDK receives an error response from the Tone Analyzer service, it generates an ApiException that contains the following fields.

Field Description
code The HTTP response code that is returned.
message A message that describes the error.
info A dictionary of additional information about the error.

The Go SDK generates an error for any unsuccessful service instantiation and method invocation. You can check for the error immediately. The contents of the error object are as shown in the following table.

Error

Field Description
code The HTTP response code that is returned.
message A message that describes the error.

The Swift SDK returns a WatsonError in the completionHandler any unsuccessful method invocation. This error type is an enum that conforms to LocalizedError and contains an errorDescription property that returns an error message. Some of the WatsonError cases contain associated values that reveal more information about the error.

Field Description
errorDescription A message that describes the error.

When the .NET Standard SDK receives an error response from the Tone Analyzer service, it generates a ServiceResponseException that contains the following fields.

Field Description
Message A message that describes the error.
CodeDescription The HTTP response code that is returned.

When the Unity SDK receives an error response from the Tone Analyzer service, it generates an IBMError that contains the following fields.

Field Description
Url The URL that generated the error.
StatusCode The HTTP response code returned.
ErrorMessage A message that describes the error.
Response The contents of the response from the server.
ResponseHeaders A dictionary of headers returned by the request.

Example error handling

try {
  // Invoke a Tone Analyzer method
} catch (NotFoundException e) {
  // Handle Not Found (404) exception
} catch (RequestTooLargeException e) {
  // Handle Request Too Large (413) exception
} catch (ServiceResponseException e) {
  // Base class for all exceptions caused by error responses from the service
  System.out.println("Service returned status code "
    + e.getStatusCode() + ": " + e.getMessage());
}

Example error handling

toneAnalyzer.method(params)
  .catch(err => {
    console.log('error:', err);
  });

Example error handling

from ibm_watson import ApiException
try:
    # Invoke a Tone Analyzer method
except ApiException as ex:
    print "Method failed with status code " + str(ex.code) + ": " + ex.message

Example error handling

require "ibm_watson"
begin
  # Invoke a Tone Analyzer method
rescue IBMWatson::ApiException => ex
  print "Method failed with status code #{ex.code}: #{ex.error}"
end

Example error handling

import "github.com/watson-developer-cloud/go-sdk/toneanalyzerv3"

// Instantiate a service
toneAnalyzer, toneAnalyzerErr := toneanalyzerv3.NewToneAnalyzerV3(&toneAnalyzerv3.ToneAnalyzerV3Options{})

// Check for errors
if toneAnalyzerErr != nil {
  panic(toneAnalyzerErr)
}

// Call a method
response, responseErr := toneAnalyzer.methodName(&methodOptions)

// Check for errors
if responseErr != nil {
  panic(responseErr)
}

Example error handling

toneAnalyzer.method() {
  response, error in

  if let error = error {
    switch error {
    case let .http(statusCode, message, metadata):
      switch statusCode {
      case .some(404):
        // Handle Not Found (404) exception
        print("Not found")
      case .some(413):
        // Handle Request Too Large (413) exception
        print("Payload too large")
      default:
        if let statusCode = statusCode {
          print("Error - code: \(statusCode), \(message ?? "")")
        }
      }
    default:
      print(error.localizedDescription)
    }
    return
  }

  guard let result = response?.result else {
    print(error?.localizedDescription ?? "unknown error")
    return
  }

  print(result)
}

Example error handling

try
{
    // Invoke a Watson toneAnalyzer method
}
catch(ServiceResponseException e)
{
    Console.WriteLine("Error: " + e.Message);
}
catch (Exception e)
{
    Console.WriteLine("Error: " + e.Message);
}

Example error handling

// Invoke a method
toneAnalyzer.MethodName(Callback, Parameters);

// Check for errors
private void Callback(DetailedResponse<ExampleResponse> response, IBMError error)
{
    if (error == null)
    {
        Log.Debug("ExampleCallback", "Response received: {0}", response.Response);
    }
    else
    {
        Log.Debug("ExampleCallback", "Error received: {0}, {1}, {3}", error.StatusCode, error.ErrorMessage, error.Response);
    }
}

Data handling

Additional headers

Some Watson services accept special parameters in headers that are passed with the request.

You can pass request header parameters in all requests or in a single request to the service.

To pass a request header, use the --header (-H) option with a curl request.

To pass header parameters with every request, use the setDefaultHeaders method of the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, use the addHeader method as a modifier on the request before you execute it.

To pass header parameters with every request, specify the headers parameter when you create the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, use the headers method as a modifier on the request before you execute it.

To pass header parameters with every request, specify the set_default_headers method of the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, include headers as a dict in the request.

To pass header parameters with every request, specify the add_default_headers method of the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, specify the headers method as a chainable method in the request.

To pass header parameters with every request, specify the SetDefaultHeaders method of the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, specify the Headers as a map in the request.

To pass header parameters with every request, add them to the defaultHeaders property of the service object. See Data collection for an example use of this method.

To pass header parameters in a single request, pass the headers parameter to the request method.

To pass header parameters in a single request, use the WithHeader() method as a modifier on the request before you execute it.

To pass header parameters in a single request, use the WithHeader() method as a modifier on the request before you execute it.

Example header parameter in a request

curl -u "apikey:{apikey}" -X {request_method} --header "Request-Header: {header_value}" "{url}/{method}"

Example header parameter in a request

ReturnType returnValue = toneAnalyzer.methodName(parameters)
  .addHeader("Custom-Header", "{header_value}")
  .execute();

Example header parameter in a request

const parameters = {
  {parameters}
};

toneAnalyzer.methodName(
  parameters,
  headers: {
    'Custom-Header': '{header_value}'
  })
   .then(result => {
    console.log(response);
  })
  .catch(err => {
    console.log('error:', err);
  });

Example header parameter in a request

response = tone_analyzer.methodName(
    parameters,
    headers = {
        'Custom-Header': '{header_value}'
    })

Example header parameter in a request

response = tone_analyzer.headers(
  "Custom-Header" => "{header_value}"
).methodName(parameters)

Example header parameter in a request

response, _ := toneanalyzerv3.methodName(
  &methodOptions{
    Headers: map[string]string{
      "Accept": "application/json",
    },
  },
)

Example header parameter in a request

let customHeader: [String: String] = ["Custom-Header": "{header_value}"]
toneAnalyzer.methodName(parameters, headers: customHeader) {
  response, error in
}

Example header parameter in a request

IamConfig iamConfig = new IamConfig(
    apikey: "{apikey}"
    );

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", iamConfig);
toneAnalyzer.SetEndpoint("{url}");
toneAnalyzer.WithHeader("Custom-Header", "header_value");

Example header parameter in a request

IamTokenOptions tokenOptions = new IamTokenOptions()
{
    IamApiKey = "{apikey}"
};
Credentials credentials = new Credentials(tokenOptions);
while (!credentials.HasTokenData())
{
    yield return null;
}

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "{url}";
toneAnalyzer.WithHeader("Custom-Header", "header_value");

Response details

The Tone Analyzer service might return information to the application in response headers.

To access all response headers that the service returns, include the --include (-i) option with a curl request. To see detailed response data for the request, including request headers, response headers, and additional debugging information, include the --verbose (-v) option with the request.

Example request to access response headers

curl -u "apikey:{apikey}" -X {request_method} --include "{url}/{method}"

To access information in the response headers, use one of the request methods that returns details with the response: executeWithDetails(), enqueueWithDetails(), or rxWithDetails(). These methods return a Response<T> object, where T is the expected response model. Use the getResult() method to access the response object for the method, and use the getHeaders() method to access information in response headers.

Example request to access response headers

Response<ReturnType> response = toneAnalyzer.methodName(parameters)
  .executeWithDetails();
// Access response from methodName
ReturnType returnValue = response.getResult();
// Access information in response headers
Headers responseHeaders = response.getHeaders();

To access information in the response headers, add the return_response parameter set to true and specify the headers attribute on the response object that is returned by the method. To access information in the response object, use the following properties.

Property Description
result Returns the response for the service-specific method.
headers Returns the response header information.
status Returns the HTTP status code.

Example request to access response headers

const parameters = {
  {parameters}
};

parameters.return_response = true;

toneAnalyzer.methodName(parameters)
  .then(response => {
    console.log(response.headers);
  })
  .catch(err => {
    console.log('error:', err);
  });

The return value from all service methods is a DetailedResponse object. To access information in the result object or response headers, use the following methods.

DetailedResponse

Method Description
get_result() Returns the response for the service-specific method.
get_headers() Returns the response header information.
get_status_code() Returns the HTTP status code.

Example request to access response headers

tone_analyzer.set_detailed_response(True)
response = tone_analyzer.methodName(parameters)
# Access response from methodName
print(json.dumps(response.get_result(), indent=2))
# Access information in response headers
print(response.get_headers())
# Access HTTP response status
print(response.get_status_code())

The return value from all service methods is a DetailedResponse object. To access information in the response object, use the following properties.

DetailedResponse

Property Description
result Returns the response for the service-specific method.
headers Returns the response header information.
status Returns the HTTP status code.

Example request to access response headers

response = tone_analyzer.methodName(parameters)
# Access response from methodName
print response.result
# Access information in response headers
print response.headers
# Access HTTP response status
print response.status

The return value from all service methods is a DetailedResponse object. To access information in the response object or response headers, use the following methods.

DetailedResponse

Method Description
GetResult() Returns the response for the service-specific method.
GetHeaders() Returns the response header information.
GetStatusCode() Returns the HTTP status code.

Example request to access response headers

import "github.com/IBM/go-sdk-core/core"
response, _ := toneanalyzerv3.methodName(&methodOptions{})

// Access result
core.PrettyPrint(response.GetResult(), "Result ")

// Access response headers
core.PrettyPrint(response.GetHeaders(), "Headers ")

// Access status code
core.PrettyPrint(response.GetStatusCode(), "Status Code ")

All response data is available in the WatsonResponse<T> object that is returned in each method's completionHandler.

Example request to access response headers

toneAnalyzer.methodName(parameters) {
  response, error in

  guard let result = response?.result else {
    print(error?.localizedDescription ?? "unknown error")
    return
  }
  print(result) // The data returned by the service
  print(response?.statusCode)
  print(response?.headers)
}

The response contains fields for response headers, response JSON, and the status code.

DetailedResponse

Property Description
Result Returns the result for the service-specific method.
Response Returns the raw JSON response for the service-specific method.
Headers Returns the response header information.
StatusCode Returns the HTTP status code.

Example request to access response headers

var results = toneAnalyzer.MethodName(parameters);

var result = results.Result;            //  The result object
var responseHeaders = results.Headers;  //  The response headers
var responseJson = results.Response;    //  The raw response JSON
var statusCode = results.StatusCode;    //  The response status code

The response contains fields for response headers, response JSON, and the status code.

DetailedResponse

Property Description
Result Returns the result for the service-specific method.
Response Returns the raw JSON response for the service-specific method.
Headers Returns the response header information.
StatusCode Returns the HTTP status code.

Example request to access response headers

private void Example()
{
    toneAnalyzer.MethodName(Callback, Parameters);
}

private void Callback(DetailedResponse<ResponseType> response, IBMError error)
{
    var result = response.Result;                 //  The result object
    var responseHeaders = response.Headers;       //  The response headers
    var responseJson = reresponsesults.Response;  //  The raw response JSON
    var statusCode = response.StatusCode;         //  The response status code
}

Data collection

Request logging is disabled for the Tone Analyzer service. Regardless of whether you set the X-Watson-Learning-Opt-Out request header, the service does not log or retain data from requests and responses.

Example request

curl -u "apikey:{apikey}" -H "X-Watson-Learning-Opt-Out: true" "{url}/{method}"

Example request

Map<String, String> headers = new HashMap<String, String>();
headers.put("X-Watson-Learning-Opt-Out", "true");

toneAnalyzer.setDefaultHeaders(headers);

Example request

const ToneAnalyzerV3 = require('ibm-watson/tone-analyzer/v3');

const toneAnalyzer = new ToneAnalyzerV3({
  version: '{version}',
  iam_apikey: '{apikey}',
  url: '{url}',
  headers: {
    'X-Watson-Learning-Opt-Out': 'true'
  }
});

Example request

tone_analyzer.set_default_headers({'x-watson-learning-opt-out': "true"})

Example request

tone_analyzer.add_default_headers(headers: {"x-watson-learning-opt-out" => "true"})

Example request

import "net/http"

headers := http.Header{}
headers.Add("x-watson-learning-opt-out", "true")
toneanalyzerv3.Service.SetDefaultHeaders(headers)

Example request

toneAnalyzer.defaultHeaders["X-Watson-Learning-Opt-Out"] = "true"

Example request

IamConfig config = new IamConfig(
    apikey: "{apikey}"
    );

ToneAnalyzer toneAnalyzer = new ToneAnalyzer("{version}", config);
toneAnalyzer.SetEndpoint("{url}");
toneAnalyzer.WithHeader("X-Watson-Learning-Opt-Out", "true");

Example request

IamTokenOptions tokenOptions = new IamTokenOptions()
{
    IamApiKey = "{apikey}"
};
Credentials credentials = new Credentials(tokenOptions,);
while (!credentials.HasTokenData())
{
    yield return null;
}

ToneAnalyzerService toneAnalyzer = new ToneAnalyzerService("{version}", credentials);
toneAnalyzer.Url = "{url}";
toneAnalyzer.WithHeader("X-Watson-Learning-Opt-Out", "true");

Synchronous and asynchronous requests

The Java SDK supports both synchronous (blocking) and asynchronous (non-blocking) execution of service methods. All service methods implement the ServiceCall interface.

  • To call a method synchronously, use the execute method of the ServiceCall interface. You can call the execute method directly from an instance of the service.
  • To call a method asynchronously, use the enqueue method of the ServiceCall interface to receive a callback when the response arrives. The ServiceCallback interface of the method's argument provides onResponse and onFailure methods that you override to handle the callback.

The Ruby SDK supports both synchronous (blocking) and asynchronous (non-blocking) execution of service methods. All service methods implement the Concurrent::Async module. When you use the synchronous or asynchronous methods, an IVar object is returned. You access the DetailedResponse object by calling ivar_object.value.

For more information about the Ivar object, see the IVar class docs.

  • To call a method synchronously, either call the method directly or use the .await chainable method of the Concurrent::Async module.

    Calling a method directly (without .await) returns a DetailedResponse object.

  • To call a method asynchronously, use the .async chainable method of the Concurrent::Async module.

You can call the .await and .async methods directly from an instance of the service.

Example synchronous request

ReturnType returnValue = toneAnalyzer.method(parameters).execute();

Example asynchronous request

toneAnalyzer.method(parameters).enqueue(new ServiceCallback<ReturnType>() {
  @Override public void onResponse(ReturnType response) {
    . . .
  }
  @Override public void onFailure(Exception e) {
    . . .
  }
});

Example synchronous request

response = tone_analyzer.method_name(parameters)

or

response = tone_analyzer.await.method_name(parameters)

Example asynchronous request

response = tone_analyzer.async.method_name(parameters)

Related information

Methods

Analyze general tone (GET)

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in plain text format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Use this GET method to analyze smaller quantities of plain text content. Use the Analyze general tone POST method to analyze larger amounts of content in any of the available formats.

Per the HTTP specification, the default encoding for plain text is ISO-8859-1 (effectively, the ASCII character set). Include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8.

See also: Using the general-purpose endpoint.

GET /v3/tone
Request

Custom Headers

  • Content-Language
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • Accept-Language
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

Query Parameters

  • text
    string

    Plain text input that contains the content to be analyzed. You must URL-encode the input.

  • version
    string

    The version of the API that you want to use as a date in the form YYYY-MM-DD; for example, specify 2017-09-21 for September 21, 2017 (the latest version).

    The date that you specify does not need to match a version of the service exactly; the service uses the version that is no later than the date you provide. If you specify a date that is earlier than 2016-05-19, the service uses that version of the API. If you specify a date that is in the future or otherwise later than the most recent version, the service uses the latest version.

  • sentences
    boolean

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    string[]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

Response

Response Body

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

Status Code

  • 200

    OK. The request succeeded. If the input is partially correct, the response can include warning or error fields with appropriate messages.

  • 400

    Bad Request. A required input parameter is null or a specified input parameter or header value is invalid or not supported.

  • 401

    Unauthorized. Access is denied due to invalid service credentials.

  • 404

    Not Found. A requested item or parameter does not exist.

  • 429

    Too Many Requests. The service is throttling your request because your IBM Cloud ID submitted more than 1200 requests per minute.

  • 500

    Internal Server Error. The service encountered an internal error.

Example responses

Analyze general tone

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

Use the general-purpose endpoint to analyze the tone of your input content. The service analyzes the content for emotional and language tones. The method always analyzes the tone of the full document; by default, it also analyzes the tone of each individual sentence of the content.

You can submit no more than 128 KB of total input content and no more than 1000 individual sentences in JSON, plain text, or HTML format. The service analyzes the first 1000 sentences for document-level analysis and only the first 100 sentences for sentence-level analysis.

Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8; per the HTTP specification, the default encoding for plain text and HTML is ISO-8859-1 (effectively, the ASCII character set). When specifying a content type of plain text or HTML, include the charset parameter to indicate the character encoding of the input text; for example: Content-Type: text/plain;charset=utf-8. For text/html, the service removes HTML tags and analyzes only the textual content.

See also: Using the general-purpose endpoint.

POST /v3/tone
(toneAnalyzer *ToneAnalyzerV3) Tone(toneOptions *ToneOptions) (*core.DetailedResponse, error)
ServiceCall<ToneAnalysis> tone(ToneOptions toneOptions)
tone(params, [callback()])
tone(self, tone_input, sentences=None, tones=None, content_language=None, accept_language=None, content_type=None, **kwargs)
tone(tone_input:, sentences: nil, tones: nil, content_language: nil, accept_language: nil, content_type: nil)
func tone(
    toneContent: ToneContent,
    sentences: Bool? = nil,
    tones: [String]? = nil,
    contentLanguage: String? = nil,
    acceptLanguage: String? = nil,
    headers: [String: String]? = nil,
    completionHandler: @escaping (WatsonResponse<ToneAnalysis>?, WatsonError?) -> Void)
Tone(ToneInput toneInput, bool? sentences = null, List<string> tones = null, string contentLanguage = null, string acceptLanguage = null, string contentType = null)
Tone(Callback<ToneAnalysis> callback, ToneInput toneInput, bool? sentences = null, List<string> tones = null, string contentLanguage = null, string acceptLanguage = null, string contentType = null)
Request

Instantiate the ToneOptions struct and set the fields to provide parameter values for the Tone method.

Use the ToneOptions.Builder to create a ToneOptions object that contains the parameter values for the tone method.

Custom Headers

  • Content-Language
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • Accept-Language
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • Content-Type
    string

    Allowable values: [application/json,text/plain,text/html]

Query Parameters

  • version
    string

    The version of the API that you want to use as a date in the form YYYY-MM-DD; for example, specify 2017-09-21 for September 21, 2017 (the latest version).

    The date that you specify does not need to match a version of the service exactly; the service uses the version that is no later than the date you provide. If you specify a date that is earlier than 2016-05-19, the service uses that version of the API. If you specify a date that is in the future or otherwise later than the most recent version, the service uses the latest version.

  • sentences
    boolean

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    string[]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

Request Body

ToneInput

JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

ToneOptions

The Tone options.

ToneOptions

The tone options.

parameters

  • tone_input
    ToneInput | string

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    boolean

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    string[]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • content_language
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • content_type
    string

    The type of the input. A character encoding can be specified by including a charset parameter. For example, 'text/plain;charset=utf-8'.

    Allowable values: [application/json,text/plain,text/html]

parameters

  • tone_input
    ToneInput

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    bool

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    list[str]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • content_language
    str

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    str

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • content_type
    str

    The type of the input. A character encoding can be specified by including a charset parameter. For example, 'text/plain;charset=utf-8'.

    Allowable values: [application/json,text/plain,text/html]

parameters

  • tone_input
    ToneInput

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    Boolean

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    Array[String]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • content_language
    String

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    String

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • content_type
    String

    The type of the input. A character encoding can be specified by including a charset parameter. For example, 'text/plain;charset=utf-8'.

    Allowable values: [application/json,text/plain,text/html]

parameters

  • toneContent
    ToneContent

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    Bool

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    [String]

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • contentLanguage
    String

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    String

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • toneInput
    ToneInput

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    bool?

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    List<string>

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • contentLanguage
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • contentType
    string

    The type of the input. A character encoding can be specified by including a charset parameter. For example, 'text/plain;charset=utf-8'.

    Allowable values: [application/json,text/plain,text/html]

parameters

  • toneInput
    ToneInput

    JSON, plain text, or HTML input that contains the content to be analyzed. For JSON input, provide an object of type ToneInput.

  • sentences
    bool?

    Indicates whether the service is to return an analysis of each individual sentence in addition to its analysis of the full document. If true (the default), the service returns results for each sentence.

    Default: true

  • tones
    List<string>

    2017-09-21: Deprecated. The service continues to accept the parameter for backward-compatibility, but the parameter no longer affects the response.

    2016-05-19: A comma-separated list of tones for which the service is to return its analysis of the input; the indicated tones apply both to the full document and to individual sentences of the document. You can specify one or more of the valid values. Omit the parameter to request results for all three tones.

    Allowable values: [emotion,language,social]

  • contentLanguage
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

  • contentType
    string

    The type of the input. A character encoding can be specified by including a charset parameter. For example, 'text/plain;charset=utf-8'.

    Allowable values: [application/json,text/plain,text/html]

Response

Response Body

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

ToneAnalysis

The tone analysis results for the input from the general-purpose endpoint.

Status Code

  • 200

    OK. The request succeeded. If the input is partially correct, the response can include warning or error fields with appropriate messages.

  • 400

    Bad Request. A required input parameter is null or a specified input parameter or header value is invalid or not supported.

  • 401

    Unauthorized. Access is denied due to invalid service credentials.

  • 404

    Not Found. A requested item or parameter does not exist.

  • 429

    Too Many Requests. The service is throttling your request because your IBM Cloud ID submitted more than 1200 requests per minute.

  • 500

    Internal Server Error. The service encountered an internal error.

Example responses

Analyze customer-engagement tone

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

Use the customer-engagement endpoint to analyze the tone of customer service and customer support conversations. For each utterance of a conversation, the method reports the most prevalent subset of the following seven tones: sad, frustrated, satisfied, excited, polite, impolite, and sympathetic.

If you submit more than 50 utterances, the service returns a warning for the overall content and analyzes only the first 50 utterances. If you submit a single utterance that contains more than 500 characters, the service returns an error for that utterance and does not analyze the utterance. The request fails if all utterances have more than 500 characters. Per the JSON specification, the default character encoding for JSON content is effectively always UTF-8.

See also: Using the customer-engagement endpoint.

POST /v3/tone_chat
(toneAnalyzer *ToneAnalyzerV3) ToneChat(toneChatOptions *ToneChatOptions) (*core.DetailedResponse, error)
ServiceCall<UtteranceAnalyses> toneChat(ToneChatOptions toneChatOptions)
toneChat(params, [callback()])
tone_chat(self, utterances, content_language=None, accept_language=None, **kwargs)
tone_chat(utterances:, content_language: nil, accept_language: nil)
func toneChat(
    utterances: [Utterance],
    contentLanguage: String? = nil,
    acceptLanguage: String? = nil,
    headers: [String: String]? = nil,
    completionHandler: @escaping (WatsonResponse<UtteranceAnalyses>?, WatsonError?) -> Void)
ToneChat(List<Utterance> utterances, string contentLanguage = null, string acceptLanguage = null)
ToneChat(Callback<UtteranceAnalyses> callback, List<Utterance> utterances, string contentLanguage = null, string acceptLanguage = null)
Request

Instantiate the ToneChatOptions struct and set the fields to provide parameter values for the ToneChat method.

Use the ToneChatOptions.Builder to create a ToneChatOptions object that contains the parameter values for the toneChat method.

Custom Headers

  • Content-Language
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • Accept-Language
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

Query Parameters

  • version
    string

    The version of the API that you want to use as a date in the form YYYY-MM-DD; for example, specify 2017-09-21 for September 21, 2017 (the latest version).

    The date that you specify does not need to match a version of the service exactly; the service uses the version that is no later than the date you provide. If you specify a date that is earlier than 2016-05-19, the service uses that version of the API. If you specify a date that is in the future or otherwise later than the most recent version, the service uses the latest version.

Request Body

ToneChatInput

An object that contains the content to be analyzed.

ToneChatOptions

The ToneChat options.

ToneChatOptions

The toneChat options.

parameters

  • utterances
    Utterance[]

    An array of Utterance objects that provides the input content that the service is to analyze.

  • content_language
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • utterances
    list[Utterance]

    An array of Utterance objects that provides the input content that the service is to analyze.

  • content_language
    str

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    str

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • utterances
    Array[Utterance]

    An array of Utterance objects that provides the input content that the service is to analyze.

  • content_language
    String

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • accept_language
    String

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • utterances
    [Utterance]

    An array of Utterance objects that provides the input content that the service is to analyze.

  • contentLanguage
    String

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    String

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • utterances
    List<Utterance>

    An array of Utterance objects that provides the input content that the service is to analyze.

  • contentLanguage
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

parameters

  • utterances
    List<Utterance>

    An array of Utterance objects that provides the input content that the service is to analyze.

  • contentLanguage
    string

    The language of the input text for the request: English or French. Regional variants are treated as their parent language; for example, en-US is interpreted as en. The input content must match the specified language. Do not submit content that contains both languages. You can use different languages for Content-Language and Accept-Language.

    • 2017-09-21: Accepts en or fr.
    • 2016-05-19: Accepts only en.

    Allowable values: [en,fr]

    Default: en

  • acceptLanguage
    string

    The desired language of the response. For two-character arguments, regional variants are treated as their parent language; for example, en-US is interpreted as en. You can use different languages for Content-Language and Accept-Language.

    Allowable values: [ar,de,en,es,fr,it,ja,ko,pt-br,zh-cn,zh-tw]

    Default: en

Response

Response Body

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

UtteranceAnalyses

The results of the analysis for the utterances of the input content.

Status Code

  • 200

    OK. The request succeeded. If the input is partially correct, the response can include warning or error fields with appropriate messages.

  • 400

    Bad Request. A required input parameter is null or a specified input parameter or header value is invalid or not supported. The response is also returned if all utterances of the input have more than 500 characters.

  • 401

    Unauthorized. Access is denied due to invalid service credentials.

  • 404

    Not Found. A requested item or parameter does not exist.

  • 429

    Too Many Requests. The service is throttling your request because your IBM Cloud ID submitted more than 1200 requests per minute.

  • 500

    Internal Server Error. The service encountered an internal error.

Example responses