☄️ Node.js library to access IBM Watson services.
Branch: master
Clone or download
semantic-release-bot chore(release): 3.18.1 [skip ci]
## [3.18.1](v3.18.0...v3.18.1) (2019-02-14)

### Bug Fixes

* use dotenv v5 to maintain node 4.x compatibility ([c311651](c311651))
Latest commit c7ce58b Feb 14, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github docs: Add information about commit message guidelines Jun 28, 2018
assistant chore(assistant): make corrections Feb 5, 2019
authorization feat: auth service now supports returning IAM tokens Jul 9, 2018
compare-comply feat(compare-comply): new constants and new model properties added Feb 5, 2019
conversation docs: add deprecation messages for conversation v1 and language trans… Nov 8, 2018
dialog Add support for IAM tokens (#672) Apr 23, 2018
discovery feat(discovery): add method `getStopwordListStatus` Feb 5, 2019
dist added support for building and minifying browser bundles. Also added … Jul 27, 2016
examples docs: add documentation in the readme for reading credentials file Feb 1, 2019
iam-token-manager Provides support for delete user data & visual recognition url change ( May 30, 2018
language-translator refactor: send formatted headers for sdk metrics Jan 30, 2019
lib chore: Add setServiceUrl method to base service class Feb 12, 2019
natural-language-classifier refactor: send formatted headers for sdk metrics Jan 30, 2019
natural-language-understanding refactor: send formatted headers for sdk metrics Jan 30, 2019
personality-insights refactor: send formatted headers for sdk metrics Jan 30, 2019
scripts chore(language-translator): remove language translator v2 as it is no… Dec 6, 2018
speech-to-text feat(speech-to-text): optional parameter `force` added to the method … Feb 5, 2019
test chore: Add setServiceUrl method to base service class Feb 12, 2019
text-to-speech refactor: send formatted headers for sdk metrics Jan 30, 2019
tone-analyzer refactor: send formatted headers for sdk metrics Jan 30, 2019
visual-recognition docs(visual-recognition): docs updates Feb 5, 2019
.editorconfig adding .editorconfig file to make my editor conform to the project's … Mar 19, 2015
.eslintignore Trisha fix jenkins (#601) Dec 20, 2017
.eslintrc.js test: convert integration tests to use jest Nov 8, 2018
.gitattributes Fix line endings and missing copyright Feb 12, 2018
.gitignore build: allow for encryption of multiple files Dec 6, 2018
.npmignore 🐎 Updates to SDK to precent TypeScript compilation errors Jan 31, 2018
.pre-commit-config.yaml build: add precommit hook for detect-secrets Jan 17, 2019
.prettierrc fix(Prettier,tslint): Regeneration of services and tslint support (#638) Mar 5, 2018
.releaserc ci: modify .releaserc to continously update the changelog Aug 1, 2018
.secrets.baseline build: add secrets baseline file for use with detect-secrets Jan 17, 2019
.travis.yml build: check installed packages for incompatibility with supported no… Feb 5, 2019
CHANGELOG.md chore(release): 3.18.1 [skip ci] Feb 14, 2019
LICENSE [ci skip] clean up license Oct 17, 2016
README.md docs: update test section of readme Feb 12, 2019
RELEASE.md docs(release): Update release steps Jun 28, 2018
commitlint.config.js chore: fix linting errors Sep 10, 2018
dependency-lint.yml Fix dependency-lint config to eliminate false lint errors Feb 12, 2018
index.ts chore(language-translator): remove language translator v2 as it is no… Dec 6, 2018
package-lock.json chore(release): 3.18.1 [skip ci] Feb 14, 2019
package.json chore(release): 3.18.1 [skip ci] Feb 14, 2019
secrets.tar.enc test: use new instance of cnc for testing Jan 7, 2019
tsconfig.json feat: add support for Compare and Comply service Dec 6, 2018
tslint.json fix(Prettier,tslint): Regeneration of services and tslint support (#638) Mar 5, 2018

README.md

Watson APIs Node.js SDK

Build Status codecov Slack npm-version npm-downloads semantic-release

Node.js client library to use the Watson APIs.

Table of Contents

Before you begin

Installation

npm install watson-developer-cloud

Usage

The examples folder has basic and advanced examples. The examples within each service assume that you already have service credentials.

Credentials are checked for in the following order:

  1. Hard-coded or programatic credentials passed to the service constructor

  2. Environment variables:

  • SERVICE_NAME_USERNAME and SERVICE_NAME_PASSWORD environment properties (or SERVICE_NAME_API_KEY when appropriate) and, optionally, SERVICE_NAME_URL
  • If using IAM: SERVICE_NAME_IAM_APIKEY and optionally SERVICE_NAME_IAM_URL, or SERVICE_NAME_IAM_ACCESS_TOKEN
  1. IBM-Cloud-supplied credentials (via the VCAP_SERVICES JSON-encoded environment property)

If you run your app in IBM Cloud, the SDK gets credentials from the VCAP_SERVICES environment variable.

Client-side usage

See the examples/ folder for Browserify and Webpack client-side SDK examples (with server-side generation of auth tokens.)

Note: not all services currently support CORS, and therefore not all services can be used client-side. Of those that do, most require an auth token to be generated server-side via the Authorization Service.

Authentication

Watson services are migrating to token-based Identity and Access Management (IAM) authentication.

  • With some service instances, you authenticate to the API by using IAM.
  • In other instances, you authenticate by providing the username and password for the service instance.

Getting credentials

To find out which authentication to use, view the service credentials. You find the service credentials for authentication the same way for all Watson services:

  1. Go to the IBM Cloud Dashboard page.
  2. Either click an existing Watson service instance in your resource list or click Create resource > AI and create a service instance.
  3. Click on the Manage item in the left nav bar of your service instance.

On this page, you should be able to see your credentials for accessing your service instance.

In your code, you can use these values in the service constructor or with a method call after instantiating your service.

Supplying credentials

There are two ways to supply the credentials you found above to the SDK for authentication:

Credentials file (easier!)

With a credentials file, you just need to put the file in the right place and the SDK will do the work of parsing it and authenticating. You can get this file by clicking the Download button for the credentials in the Manage tab of your service instance.

The file downloaded will be called ibm-credentials.env. This is the name the SDK will search for and must be preserved unless you want to configure the file path (more on that later). The SDK will look for your ibm-credentials.env file in the following places (in order):

  • Directory provided by the environment variable IBM_CREDENTIALS_FILE
  • Your system's home directory
  • Your current working directory (the directory Node is executed from)

As long as you set that up correctly, you don't have to worry about setting any authentication options in your code. So, for example, if you created and downloaded the credential file for your Discovery instance, you just need to do the following:

const DiscoveryV1 = require('watson-developer-cloud/discovery/v1');
const discovery = new DiscoveryV1({ version: '2019-02-01' });

And that's it!

If you're using more than one service at a time in your code and get two different ibm-credentials.env files, just put the contents together in one ibm-credentials.env file and the SDK will handle assigning credentials to their appropriate services.

If you would like to configure the location/name of your credential file, you can set an environment variable called IBM_CREDENTIALS_FILE. This will take precedence over the locations specified above. Here's how you can do that:

export IBM_CREDENTIALS_FILE="<path>"

where <path> is something like /home/user/Downloads/<file_name>.env. If you just provide a path to a directory, the SDK will look for a file called ibm-credentials.env in that directory.

Manually

The SDK also supports setting credentials manually in your code. You will either use IAM credentials or Basic Authentication (username/password) credentials.

IAM

Some services use token-based Identity and Access Management (IAM) authentication. IAM authentication uses a service API key to get an access token that is passed with the call. Access tokens are valid for approximately one hour and must be regenerated.

You supply either an IAM service API key or an access token:

  • Use the API key to have the SDK manage the lifecycle of the access token. The SDK requests an access token, ensures that the access token is valid, and refreshes it if necessary.
  • Use the access token if you want to manage the lifecycle yourself. For details, see Authenticating with IAM tokens. If you want to switch to API key, override your stored IAM credentials with an IAM API key.
Supplying the IAM API key
// in the constructor, letting the SDK manage the IAM token
const discovery = new DiscoveryV1({
  url: '<service_url>',
  version: '<version-date>',
  iam_apikey: '<iam_api_key>',
  iam_url: '<iam_url>', // optional - the default value is https://iam.bluemix.net/identity/token
});
Supplying the access token
// in the constructor, assuming control of managing IAM token
const discovery = new DiscoveryV1({
  url: '<service_url>',
  version: '<version-date>',
  iam_access_token: '<access-token>'
});
// after instantiation, assuming control of managing IAM token
const discovery = new DiscoveryV1({
  url: '<service_url>',
  version: '<version-date>'
});

discovery.setAccessToken('<access-token>')

Username and password

var DiscoveryV1 = require('watson-developer-cloud/discovery/v1');

var discovery = new DiscoveryV1({
    version: '{version}',
    username: '{username}',
    password: '{password}'
  });

Setting the service URL

You can set the service URL by calling the setServiceUrl() method.

const discovery = new DiscoveryV1({
  version: '<version-date>'
});

discovery.setServiceUrl('https://gateway-wdc.watsonplatform.net/discovery/api');

Sending request headers

Custom headers can be passed with any request. Each method has an optional parameter headers which can be used to pass in these custom headers, which can override headers that we use as parameters.

For example, this is how you can pass in custom headers to Watson Assistant service. In this example, the 'custom' value for 'Accept-Language' will override the default header for 'Accept-Language', and the 'Custom-Header' while not overriding the default headers, will additionally be sent with the request.

var assistant = new watson.AssistantV1({
/* username, password, version, url, etc... */
});

assistant.message({
  workspace_id: 'something',
  input: {'text': 'Hello'},
  headers: {
    'Custom-Header': 'custom',
    'Accept-Language': 'custom'

  }
},  function(err, result, response) {
  if (err)
    console.log('error:', err);
  else
    console.log(JSON.stringify(result, null, 2));
});

Parsing HTTP response

To retrieve the HTTP response, all methods can be called with a callback function with three parameters, with the third being the response. Users for example may retrieve the response headers with this usage pattern.

Here is an example of how to access the response headers for Watson Assistant:

var assistant = new watson.AssistantV1({
/* username, password, version, url, etc... */
});

assistant.message(params,  function(err, result, response) {
  if (err)
    console.log('error:', err);
  else
    console.log(response.headers);
});

Data collection opt-out

By default, all requests are logged. This can be disabled of by setting the X-Watson-Learning-Opt-Out header when creating the service instance:

var myInstance = new watson.WhateverServiceV1({
  /* username, password, version, url, etc... */
  headers: {
    "X-Watson-Learning-Opt-Out": true
  }
});

Configuring the HTTP client

The HTTP client can be configured to disable SSL verification. Note that this has serious security implications - only do this if you really mean to! ⚠️

To do this, set disable_ssl_verification to true in the service constructor, like below:

const discovery = new DiscoveryV1({
  url: '<service_url>',
  version: '<version-date>',
  iam_apikey: '<iam_api_key>',
  disable_ssl_verification: true, // this will disable SSL verification for any request made with this object
});

Documentation

You can find links to the documentation at https://console.bluemix.net/developer/watson/documentation. Find the service that you're interested in, click API reference, and then select the Node tab.

There are also auto-generated JSDocs available at http://watson-developer-cloud.github.io/node-sdk/master/

Questions

If you are having difficulties using the APIs or have a question about the Watson services, please ask a question at dW Answers or Stack Overflow.

IBM Watson services

Authorization

The Authorization service can generate auth tokens for situations where providing the service username/password is undesirable.

Tokens are valid for 1 hour and may be sent using the X-Watson-Authorization-Token header or the watson-token query param. Note that the token is supplied URL-encoded, and will not be accepted if it is double-encoded in a querystring.

NOTE: Authenticating with the X-Watson-Authorization-Token header or the watson-token query param is now deprecated. The token continues to work with Cloud Foundry services, but is not supported for services that use Identity and Access Management (IAM) authentication. For details see Authenticating with IAM tokens or the README in the IBM Watson SDK you use. The Authorization SDK now supports returning IAM Access Tokens when instantiated with an IAM API key.

var watson = require('watson-developer-cloud');

// to get an IAM Access Token
var authorization = new watson.AuthorizationV1({
  iam_apikey: '<Service API key>',
  iam_url: '<IAM endpoint URL - OPTIONAL>',
});

authorization.getToken(function (err, token) {
  if (!token) {
    console.log('error:', err);
  } else {
    // Use your token here
  }
});

// to get a Watson Token - NOW DEPRECATED
var authorization = new watson.AuthorizationV1({
  username: '<Text to Speech username>',
  password: '<Text to Speech password>',
  url: 'https://stream.watsonplatform.net/authorization/api', // Speech tokens
});

authorization.getToken({
  url: 'https://stream.watsonplatform.net/text-to-speech/api'
},
function (err, token) {
  if (!token) {
    console.log('error:', err);
  } else {
    // Use your token here
  }
});

Assistant v2

Use the Assistant service to determine the intent of a message.

Note: You must first create a workspace via IBM Cloud. See the documentation for details.

var AssistantV2 = require('watson-developer-cloud/assistant/v2');

var assistant = new AssistantV2({
  username: '<username>',
  password: '<password>',
  url: 'https://gateway.watsonplatform.net/assistant/api/',
  version: '2018-09-19'
});

assistant.message(
  {
    input: { text: "What's the weather?" },
    assistant_id: '<assistant id>',
    session_id: '<session id>',
  },
  function(err, response) {
    if (err) {
      console.error(err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Assistant v1

Use the Assistant service to determine the intent of a message.

Note: You must first create a workspace via IBM Cloud. See the documentation for details.

var AssistantV1 = require('watson-developer-cloud/assistant/v1');

var assistant = new AssistantV1({
  username: '<username>',
  password: '<password>',
  url: 'https://gateway.watsonplatform.net/assistant/api/',
  version: '2018-02-16'
});

assistant.message(
  {
    input: { text: "What's the weather?" },
    workspace_id: '<workspace id>'
  },
  function(err, response) {
    if (err) {
      console.error(err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Compare Comply

Use the Compare Comply service to compare and classify documents.

const fs = require('fs');
const CompareComplyV1 = require('watson-developer-cloud/compare-comply/v1');

const compareComply = new CompareComplyV1({
  iam_apikey: '<iam_apikey>',
  url: 'https://gateway.watsonplatform.net/compare-comply/api',
  version: '2018-12-06'
});

compareComply.compareDocuments(
  {
      file_1: fs.createReadStream('<path-to-file-1>'),
      file_1_filename: '<filename-1>',
      file_1_label: 'file-1',
      file_2: fs.createReadStream('<path-to-file-2>'),
      file_2_filename: '<filename-2>',
      file_2_label: 'file-2',
  },
  function(err, response) {
    if (err) {
      console.error(err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Conversation

This service has been renamed to Assistant.

Discovery

Use the Discovery Service to search and analyze structured and unstructured data.

var DiscoveryV1 = require('watson-developer-cloud/discovery/v1');

var discovery = new DiscoveryV1({
  username: '<username>',
  password: '<password>',
  url: 'https://gateway.watsonplatform.net/discovery/api/',
  version: '2017-09-01'
});

discovery.query(
  {
    environment_id: '<environment_id>',
    collection_id: '<collection_id>',
    query: 'my_query'
  },
  function(err, response) {
    if (err) {
      console.error(err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Language Translator

Translate text from one language to another or idenfity a language using the Language Translator service.

const LanguageTranslatorV3 = require('watson-developer-cloud/language-translator/v3');

const languageTranslator = new LanguageTranslatorV3({
  iam_apikey: '<apikey>',
  url: 'https://gateway.watsonplatform.net/language-translator/api/',
  version: 'YYYY-MM-DD',
});

languageTranslator.translate(
  {
    text: 'A sentence must have a verb',
    source: 'en',
    target: 'es'
  },
  function(err, translation) {
    if (err)  {
      console.log('error:', err);
    } else  {
      console.log(JSON.stringify(translation, null, 2));
  }
);

languageTranslator.identify(
  {
    text:
      'The language translator service takes text input and identifies the language used.'
  },
  function(err, language) {
    if (err)  {
      console.log('error:', err);
    } else {
      console.log(JSON.stringify(language, null, 2));
    }
  }
);

Natural Language Classifier

Use Natural Language Classifier service to create a classifier instance by providing a set of representative strings and a set of one or more correct classes for each as training. Then use the trained classifier to classify your new question for best matching answers or to retrieve next actions for your application.

var NaturalLanguageClassifierV1 = require('watson-developer-cloud/natural-language-classifier/v1');

var classifier = new NaturalLanguageClassifierV1({
  username: '<username>',
  password: '<password>',
  url: 'https://gateway.watsonplatform.net/natural-language-classifier/api/'
});

classifier.classify(
  {
    text: 'Is it sunny?',
    classifier_id: '<classifier-id>'
  },
  function(err, response) {
    if (err) {
      console.log('error:', err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

See this example to learn how to create a classifier.

Natural Language Understanding

Use Natural Language Understanding is a collection of natural language processing APIs that help you understand sentiment, keywords, entities, high-level concepts and more.

var fs = require('fs');
var NaturalLanguageUnderstandingV1 = require('watson-developer-cloud/natural-language-understanding/v1.js');

var nlu = new NaturalLanguageUnderstandingV1({
  username: '<username>',
  password: '<password>',
  version: '2018-04-05',
  url: 'https://gateway.watsonplatform.net/natural-language-understanding/api/'
});

nlu.analyze(
  {
    html: file_data, // Buffer or String
    features: {
      concepts: {},
      keywords: {}
    }
  },
  function(err, response) {
    if (err) {
      console.log('error:', err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Personality Insights

Analyze text in English and get a personality profile by using the Personality Insights service.

var PersonalityInsightsV3 = require('watson-developer-cloud/personality-insights/v3');

var personalityInsights = new PersonalityInsightsV3({
  username: '<username>',
  password: '<password>',
  version: '2016-10-19',
  url: 'https://gateway.watsonplatform.net/personality-insights/api/'
});

personalityInsights.profile(
  {
    content: 'Enter more than 100 unique words here...',
    content_type: 'text/plain',
    consumption_preferences: true
  },
  function(err, response) {
    if (err) {
      console.log('error:', err);
    } else {
      console.log(JSON.stringify(response, null, 2));
    }
  }
);

Speech to Text

Use the Speech to Text service to recognize the text from a .wav file.

var SpeechToTextV1 = require('watson-developer-cloud/speech-to-text/v1');
var fs = require('fs');

var speechToText = new SpeechToTextV1({
  username: '<username>',
  password: '<password>',
  url: 'https://stream.watsonplatform.net/speech-to-text/api/'
});

var params = {
  // From file
  audio: fs.createReadStream('./resources/speech.wav'),
  content_type: 'audio/l16; rate=44100'
};

speechToText.recognize(params, function(err, res) {
  if (err)
    console.log(err);
  else
    console.log(JSON.stringify(res, null, 2));
});

// or streaming
fs.createReadStream('./resources/speech.wav')
  .pipe(speechToText.recognizeUsingWebSocket({ content_type: 'audio/l16; rate=44100' }))
  .pipe(fs.createWriteStream('./transcription.txt'));

Text to Speech

Use the Text to Speech service to synthesize text into an audio file.

var TextToSpeechV1 = require('watson-developer-cloud/text-to-speech/v1');
var fs = require('fs');

var textToSpeech = new TextToSpeechV1({
  username: '<username>',
  password: '<password>',
  url: 'https://stream.watsonplatform.net/text-to-speech/api/'
});

var params = {
  text: 'Hello from IBM Watson',
  voice: 'en-US_AllisonVoice', // Optional voice
  accept: 'audio/wav'
};

// Synthesize speech, correct the wav header, then save to disk
// (wav header requires a file length, but this is unknown until after the header is already generated and sent)
textToSpeech
  .synthesize(params, function(err, audio) {
    if (err) {
      console.log(err);
      return;
    }
    textToSpeech.repairWavHeader(audio);
    fs.writeFileSync('audio.wav', audio);
    console.log('audio.wav written with a corrected wav header');
});


// or, using WebSockets
textToSpeech.synthesizeUsingWebSocket(params);
synthStream.pipe(fs.createWriteStream('./audio.ogg'));
// see more information in examples/text_to_speech_websocket.js

Tone Analyzer

Use the Tone Analyzer service to analyze the emotion, writing and social tones of a text.

var ToneAnalyzerV3 = require('watson-developer-cloud/tone-analyzer/v3');

var toneAnalyzer = new ToneAnalyzerV3({
  username: '<username>',
  password: '<password>',
  version: '2016-05-19',
  url: 'https://gateway.watsonplatform.net/tone-analyzer/api/'
});

toneAnalyzer.tone(
  {
    tone_input: 'Greetings from Watson Developer Cloud!',
    content_type: 'text/plain'
  },
  function(err, tone) {
    if (err) {
      console.log(err);
    } else {
      console.log(JSON.stringify(tone, null, 2));
    }
  }
);

Visual Recognition

Use the Visual Recognition service to recognize the following picture.

var VisualRecognitionV3 = require('watson-developer-cloud/visual-recognition/v3');
var fs = require('fs');

var visualRecognition = new VisualRecognitionV3({
  url: '<service_url>',
  version: '2018-03-19',
  iam_apikey: '<iam_api_key>',
});

var params = {
  images_file: fs.createReadStream('./resources/car.png')
};

visualRecognition.classify(params, function(err, res) {
  if (err) {
    console.log(err);
  } else {
    console.log(JSON.stringify(res, null, 2));
  }
});

Composing services

Integration of Tone Analyzer with Conversation

Sample code for integrating Tone Analyzer and Conversation is provided in the examples directory.

Unauthenticated requests

By default, the library tries to use Basic Auth and will ask for api_key or username and password and send an Authorization: Basic XXXXXXX. You can avoid this by using:

use_unauthenticated.

var watson = require('watson-developer-cloud');

var assistant = new watson.AssistantV1({
  use_unauthenticated: true
});

Debug

This library relies on the request npm module writted by request to call the Watson Services. To debug the apps, add 'request' to the NODE_DEBUG environment variable:

$ NODE_DEBUG='request' node app.js

where app.js is your Node.js file.

Tests

Running all the tests:

$ npm test

Running a specific test:

$ jest '<path to test>'

Open source @ IBM

Find more open source projects on the IBM Github Page.

License

This library is licensed under Apache 2.0. Full license text is available in COPYING.

Contributing

See CONTRIBUTING.