# Watson Developer Cloud Python SDK
[](https://github.com/watson-developer-cloud/python-sdk/actions?query=workflow%3A"Build+and+Test")
[](https://github.com/watson-developer-cloud/python-sdk/actions?query=workflow%3A%22Deploy+and+Publish%22)
[](https://pypi.python.org/pypi/ibm-watson)
[](https://cla-assistant.io/watson-developer-cloud/python-sdk)
## Deprecated builds
[](https://travis-ci.org/watson-developer-cloud/python-sdk)
Python client library to quickly get started with the various [Watson APIs][wdc] services.
## Before you begin
- You need an [IBM Cloud][ibm-cloud-onboarding] account. We now only support `python 3.5` and above
## Installation
To install, use `pip` or `easy_install`:
```bash
pip install --upgrade ibm-watson
```
or
```bash
easy_install --upgrade ibm-watson
```
Note the following:
a) Versions prior to 3.0.0 can be installed using:
```bash
pip install --upgrade watson-developer-cloud
```
b) If you run into permission issues try:
```bash
sudo -H pip install --ignore-installed six ibm-watson
```
For more details see [#225](https://github.com/watson-developer-cloud/python-sdk/issues/225)
c) In case you run into problems installing the SDK in DSX, try
```
!pip install --upgrade pip
```
Restarting the kernel
For more details see [#405](https://github.com/watson-developer-cloud/python-sdk/issues/405)
## Examples
The [examples][examples] folder has basic and advanced examples. The examples within each service assume that you already have [service credentials](#getting-credentials).
## Running in IBM Cloud
If you run your app in IBM Cloud, the SDK gets credentials from the [`VCAP_SERVICES`][vcap_services] environment variable.
## 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](#iam)**.
- In other instances, you authenticate by providing the **[username and password](#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](https://cloud.ibm.com/) page.
1. Either click an existing Watson service instance in your [resource list](https://cloud.ibm.com/resources) or click [**Create resource > AI**](https://cloud.ibm.com/catalog?category=ai) and create a service instance.
1. 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.
### Supplying credentials
There are three ways to supply the credentials you found above to the SDK for authentication.
#### Credential file
With a credential file, you just need to put the file in the right place and the SDK will do the work of parsing 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):
- The top-level directory of the project you're using the SDK in
- Your system's home directory
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:
```python
discovery = DiscoveryV1(version='2019-04-30')
```
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:
```bash
export IBM_CREDENTIALS_FILE="<path>"
```
where `<path>` is something like `/home/user/Downloads/<file_name>.env`.
#### Environment Variables
Simply set the environment variables using <service name>\_<variable name> syntax. For example, using your favourite terminal, you can set environment variables for Assistant service instance:
```bash
export ASSISTANT_APIKEY="<your apikey>"
export ASSISTANT_AUTH_TYPE="iam"
```
The credentials will be loaded from the environment automatically
```python
assistant = AssistantV1(version='2018-08-01')
```
#### Manually
If you'd prefer to set authentication values manually in your code, the SDK supports that as well. The way you'll do this depends on what type of credentials your service instance gives you.
### IAM
IBM Cloud has migrated to 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 a **bearer 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](https://cloud.ibm.com/docs/watson?topic=watson-iam).
- Use a server-side to generate access tokens using your IAM API key for untrusted environments like client-side scripts. The generated access tokens will be valid for one hour and can be refreshed.
#### Supplying the API key
```python
from ibm_watson import DiscoveryV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
# In the constructor, letting the SDK manage the token
authenticator = IAMAuthenticator('apikey',
url='<iam_url>') # optional - the default value is https://iam.cloud.ibm.com/identity/token
discovery = DiscoveryV1(version='2019-04-30',
authenticator=authenticator)
discovery.set_service_url('<url_as_per_region>')
```
#### Generating bearer tokens using API key
```python
from ibm_watson import IAMTokenManager
# In your API endpoint use this to generate new bearer tokens
iam_token_manager = IAMTokenManager(apikey='<apikey>')
token = iam_token_manager.get_token()
```
##### Supplying the bearer token
```python
from ibm_watson import DiscoveryV1
from ibm_cloud_sdk_core.authenticators import BearerTokenAuthenticator
# in the constructor, assuming control of managing the token
authenticator = BearerTokenAuthenticator('your bearer token')
discovery = DiscoveryV1(version='2019-04-30',
authenticator=authenticator)
discovery.set_service_url('<url_as_per_region>')
```
### Username and password
```python
from ibm_watson import DiscoveryV1
from ibm_cloud_sdk_core.authenticators import BasicAuthenticator
authenticator = BasicAuthenticator('username', 'password')
discovery = DiscoveryV1(version='2019-04-30', authenticator=authenticator)
discovery.set_service_url('<url_as_per_region>')
```
### No Authentication
```python
from ibm_watson import DiscoveryV1
from ibm_cloud_sdk_core.authenticators import NoAuthAuthenticator
authenticator = NoAuthAuthenticator()
discovery = DiscoveryV1(version='2019-04-30', authenticator=authenticator)
discovery.set_service_url('<url_as_per_region>')
```
## Python version
Tested on Python 3.9, 3.10, and 3.11.
## Questions
If you have issues with the APIs or have a question about the Watson services, see [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-watson+python).
## Configuring the http client (Supported from v1.1.0)
To set client configs like timeout use the `set_http_config()` function and pass it a dictionary of configs. See this [documentation](https://requests.readthedocs.io/en/latest/api/) for more information about the options. All options shown except `method`, `url`, `headers`, `params`, `data`, and `auth` are configurable via `set_http_config()`. For example for a Assistant service instance
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
authenticator = IAMAuthenticator('your apikey')
assistant = AssistantV1(
version='2021-11-27',
authenticator=authenticator)
assistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')
assistant.set_http_config({'timeout': 100})
response = assistant.message(workspace_id=workspace_id, input={
'text': 'What\'s the weather like?'}).get_result()
print(json.dumps(response, indent=2))
```
### Use behind a corporate proxy
To use the SDK with any proxies you may have they can be set as shown below. For documentation on proxies see [here](https://2.python-requests.org/en/latest/user/advanced/#proxies)
See this example configuration:
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
authenticator = IAMAuthenticator('your apikey')
assistant = AssistantV1(
version='2021-11-27',
authenticator=authenticator)
assistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')
assistant.set_http_config({'proxies': {
'http': 'http://10.10.1.10:3128',
'https': 'http://10.10.1.10:1080',
}})
```
### Sending custom certificates
To send custom certificates as a security measure in your request, use the cert property of the HTTPS Agent.
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
authenticator = IAMAuthenticator('your apikey')
assistant = AssistantV1(
version='2021-11-27',
authenticator=authenticator)
assistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')
assistant.set_http_config({'cert': ('path_to_cert_file','path_to_key_file')})
```
## Disable SSL certificate verification
For ICP(IBM Cloud Private), you can disable the SSL certificate verification by:
```python
service.set_disable_ssl_verification(True)
```
Or can set it from extrernal sources. For example set in the environment variable.
```
export <service name>_DISABLE_SSL=True
```
## Setting the service url
To set the base service to be used when contacting the service
```python
service.set_service_url('my_new_service_url')
```
Or can set it from extrernal sources. For example set in the environment variable.
```
export <service name>_URL="<your url>"
```
## Sending request headers
Custom headers can be passed in any request in the form of a `dict` as:
```python
headers = {
'Custom-Header': 'custom_value'
}
```
For example, to send a header called `Custom-Header` to a call in Watson Assistant, pass
the headers parameter as:
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
authenticator = IAMAuthenticator('your apikey')
assistant = AssistantV1(
version='2018-07-10',
authenticator=authenticator)
assistant.set_service_url('https://gateway.watsonplatform.net/assistant/api')
response = assistant.list_workspaces(headers={'Custom-Header': 'custom_value'}).get_result()
```
## Parsing HTTP response information
If you would like access to some HTTP response information along with the response model, you can set the `set_detailed_response()` to `True`. Since Python SDK `v2.0`, it is set to `True`
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
authenticator = IAMAuthenticator('your apikey')
assistant = AssistantV1(
version='2018-07-10',
authenticator=authenticator)
assistant.set_service_url('https://gateway.watsonplatform.net/assistant/api')
assistant.set_detailed_response(True)
response = assistant.list_workspaces(headers={'Custom-Header': 'custom_value'}).get_result()
print(response)
```
This would give an output of `DetailedResponse` having the structure:
```python
{
'result': <response returned by service>,
'headers': { <http response headers> },
'status_code': <http status code>
}
```
You can use the `get_result()`, `get_headers()` and get_status_code() to return the result, headers and status code respectively.
## Getting the transaction ID
Every SDK call returns a response with a transaction ID in the `X-Global-Transaction-Id` header. Together the service instance region, this ID helps support teams troubleshoot issues from relevant logs.
### Suceess
```python
from ibm_watson import AssistantV1
service = AssistantV1(authenticator={my_authenticator})
response_headers = service.my_service_call().get_headers()
print(response_headers.get('X-Global-Transaction-Id'))
```
### Failure
```python
from ibm_watson import AssistantV1, ApiException
try:
service = AssistantV1(authenticator={my_authenticator})
service.my_service_call()
except ApiException as e:
print(e.global_transaction_id)
# OR
print(e.http_response.headers.get('X-Global-Transaction-Id'))
```
However, the transaction ID isn't available when the API doesn't return a response for some reason. In that case, you can set your own transaction ID in the request. For example, replace `<my-unique-transaction-id>` in the following example with a unique transaction ID.
```python
from ibm_watson import AssistantV1
service = AssistantV1(authenticator={my_authenticator})
service.my_service_call(headers={'X-Global-Transaction-Id': '<my-unique-transaction-id>'})
```
## Using Websockets
The Text to Speech service supports synthesizing text to spoken audio using web sockets with the `synthesize_using_websocket`. The Speech to Text service supports recognizing speech to text using web sockets with the `recognize_using_websocket`. These methods need a custom callback class to listen to events. Below is an example of `synthesize_using_websocket`. Note: The service accepts one request per connection.
```py
from ibm_watson.websocket import SynthesizeCallback
class MySynthesizeCallback(SynthesizeCallback):
def __init__(self):
SynthesizeCallback.__init__(self)
def on_audio_stream(self, audio_stream):
return audio_stream
def on_data(self, data):
return data
my_callback = MySynthesizeCallback()
service.synthesize_using_websocket('I like to pet dogs',
my_callback,
accept='audio/wav',
voice='en-US_AllisonVoice'
)
```
## Cloud Pak for Data
If your service instance is of CP4D, below are two ways of initializing the assistant service.
### 1) Supplying the username, password and authentication url
The SDK will manage the token for the user
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import CloudPakForDataAuthenticator
authenticator = CloudPakForDataAuthenticator(
'<your username>',
'<your password>',
'<authentication url>', # should be of the form https://{icp_cluster_host}{instance-id}/api
disable_ssl_verification=True) # Disable ssl verification for authenticator
assistant = AssistantV1(
version='<version>',
authenticator=authenticator)
assistant.set_service_url('<service url>') # should be of the form https://{icp_cluster_host}/{deployment}/assistant/{instance-id}/api
assistant.set_disable_ssl_verification(True) # MAKE SURE SSL VERIFICATION IS DISABLED
```
### 2) Supplying the access token
```python
from ibm_watson import AssistantV1
from ibm_cloud_sdk_core.authenticators import BearerTokenAuthenticator
authenticator = BearerTokenAuthenticator('your managed access token')
assistant = AssistantV1(version='<version>',
authenticator=authenticator)
assistant.set_service_url('<service url>') # should be of the form https://{icp_cluster_host}/{deployment}/assistant/{instance-id}/api
assistant.set_disable_ssl_verification(True) # MAKE SURE SSL VERIFICATION IS DISABLED
```
## Logging
### Enable logging
```python
import logging
logging.basicConfig(level=logging.DEBUG)
```
This would show output of the form:
```
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): iam.cloud.ibm.com:443
DEBUG:urllib3.connectionpool:https://iam.cloud.ibm.com:443 "POST /identity/token HTTP/1.1" 200 1809
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443
DEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 "POST /assistant/api/v1/workspaces?version=2018-07-10 HTTP/1.1" 201 None
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443
DEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 "GET /assistant/api/v1/workspaces/883a2a44-eb5f-4b1a-96b0-32a90b475ea8?version=2018-07-10&export=true HTTP/1.1" 200 None
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443
DEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 "DELETE /assistant/api/v1/workspaces/883a2a44-eb5f-4b1a-96b0-32a90b475ea8?version=2018-07-10 HTTP/1.1" 200 28
```
### Low level request and response dump
To get low level information of the requests/ responses:
```python
from http.client import HTTPConnection
HTTPConnection.debuglevel = 1
```
## Dependencies
- [requests]
- `python_dateutil` >= 2.5.3
- [responses] for testing
- Following for web sockets support in speech to text
- `websocket-client` 1.1.0
- `ibm_cloud_sdk_core` >= 3.16.2
## Contributing
See [CONTRIBUTING.md][contributing].
## License
This library is licensed under the [Apache 2.0 license][license].
Raw data
{
"_id": null,
"home_page": "https://github.com/watson-developer-cloud/python-sdk",
"name": "ibm-watson",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "language,vision,question and answer tone_analyzer,natural language classifier,text to speech,language translation,language identification,concept expansion,machine translation,personality insights,message resonance,watson developer cloud,wdc,watson,ibm,dialog,user modeling,tone analyzer,speech to text,visual recognition",
"author": "IBM Watson",
"author_email": "watdevex@us.ibm.com",
"download_url": "https://files.pythonhosted.org/packages/2f/3f/4708bf3f6d369630761fa8c230a588b2b52d2bc65211db874ffd393dff51/ibm-watson-8.0.0.tar.gz",
"platform": null,
"description": "# Watson Developer Cloud Python SDK\n\n[](https://github.com/watson-developer-cloud/python-sdk/actions?query=workflow%3A\"Build+and+Test\")\n[](https://github.com/watson-developer-cloud/python-sdk/actions?query=workflow%3A%22Deploy+and+Publish%22)\n[](https://pypi.python.org/pypi/ibm-watson)\n[](https://cla-assistant.io/watson-developer-cloud/python-sdk)\n\n## Deprecated builds\n\n[](https://travis-ci.org/watson-developer-cloud/python-sdk)\n\nPython client library to quickly get started with the various [Watson APIs][wdc] services.\n\n## Before you begin\n\n- You need an [IBM Cloud][ibm-cloud-onboarding] account. We now only support `python 3.5` and above\n\n## Installation\n\nTo install, use `pip` or `easy_install`:\n\n```bash\npip install --upgrade ibm-watson\n```\n\nor\n\n```bash\neasy_install --upgrade ibm-watson\n```\n\nNote the following:\na) Versions prior to 3.0.0 can be installed using:\n\n```bash\npip install --upgrade watson-developer-cloud\n```\n\nb) If you run into permission issues try:\n\n```bash\nsudo -H pip install --ignore-installed six ibm-watson\n```\n\nFor more details see [#225](https://github.com/watson-developer-cloud/python-sdk/issues/225)\n\nc) In case you run into problems installing the SDK in DSX, try\n\n```\n!pip install --upgrade pip\n```\n\nRestarting the kernel\n\nFor more details see [#405](https://github.com/watson-developer-cloud/python-sdk/issues/405)\n\n## Examples\n\nThe [examples][examples] folder has basic and advanced examples. The examples within each service assume that you already have [service credentials](#getting-credentials).\n\n## Running in IBM Cloud\n\nIf you run your app in IBM Cloud, the SDK gets credentials from the [`VCAP_SERVICES`][vcap_services] environment variable.\n\n## Authentication\n\nWatson services are migrating to token-based Identity and Access Management (IAM) authentication.\n\n- With some service instances, you authenticate to the API by using **[IAM](#iam)**.\n- In other instances, you authenticate by providing the **[username and password](#username-and-password)** for the service instance.\n\n### Getting credentials\n\nTo find out which authentication to use, view the service credentials. You find the service credentials for authentication the same way for all Watson services:\n\n1. Go to the IBM Cloud [Dashboard](https://cloud.ibm.com/) page.\n1. Either click an existing Watson service instance in your [resource list](https://cloud.ibm.com/resources) or click [**Create resource > AI**](https://cloud.ibm.com/catalog?category=ai) and create a service instance.\n1. Click on the **Manage** item in the left nav bar of your service instance.\n\nOn this page, you should be able to see your credentials for accessing your service instance.\n\n### Supplying credentials\n\nThere are three ways to supply the credentials you found above to the SDK for authentication.\n\n#### Credential file\n\nWith a credential file, you just need to put the file in the right place and the SDK will do the work of parsing and authenticating. You can get this file by clicking the **Download** button for the credentials in the **Manage** tab of your service instance.\n\nThe 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):\n\n- The top-level directory of the project you're using the SDK in\n- Your system's home directory\n\nAs 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:\n\n```python\ndiscovery = DiscoveryV1(version='2019-04-30')\n```\n\nAnd that's it!\n\nIf 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.\n\nIf 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:\n\n```bash\nexport IBM_CREDENTIALS_FILE=\"<path>\"\n```\n\nwhere `<path>` is something like `/home/user/Downloads/<file_name>.env`.\n\n#### Environment Variables\n\nSimply set the environment variables using <service name>\\_<variable name> syntax. For example, using your favourite terminal, you can set environment variables for Assistant service instance:\n\n```bash\nexport ASSISTANT_APIKEY=\"<your apikey>\"\nexport ASSISTANT_AUTH_TYPE=\"iam\"\n```\n\nThe credentials will be loaded from the environment automatically\n\n```python\nassistant = AssistantV1(version='2018-08-01')\n```\n\n#### Manually\n\nIf you'd prefer to set authentication values manually in your code, the SDK supports that as well. The way you'll do this depends on what type of credentials your service instance gives you.\n\n### IAM\n\nIBM Cloud has migrated to 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.\n\nYou supply either an IAM service **API key** or a **bearer token**:\n\n- 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.\n- Use the access token if you want to manage the lifecycle yourself. For details, see [Authenticating with IAM tokens](https://cloud.ibm.com/docs/watson?topic=watson-iam).\n- Use a server-side to generate access tokens using your IAM API key for untrusted environments like client-side scripts. The generated access tokens will be valid for one hour and can be refreshed.\n\n#### Supplying the API key\n\n```python\nfrom ibm_watson import DiscoveryV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\n# In the constructor, letting the SDK manage the token\nauthenticator = IAMAuthenticator('apikey',\n url='<iam_url>') # optional - the default value is https://iam.cloud.ibm.com/identity/token\ndiscovery = DiscoveryV1(version='2019-04-30',\n authenticator=authenticator)\ndiscovery.set_service_url('<url_as_per_region>')\n```\n\n#### Generating bearer tokens using API key\n\n```python\nfrom ibm_watson import IAMTokenManager\n\n# In your API endpoint use this to generate new bearer tokens\niam_token_manager = IAMTokenManager(apikey='<apikey>')\ntoken = iam_token_manager.get_token()\n```\n\n##### Supplying the bearer token\n\n```python\nfrom ibm_watson import DiscoveryV1\nfrom ibm_cloud_sdk_core.authenticators import BearerTokenAuthenticator\n\n# in the constructor, assuming control of managing the token\nauthenticator = BearerTokenAuthenticator('your bearer token')\ndiscovery = DiscoveryV1(version='2019-04-30',\n authenticator=authenticator)\ndiscovery.set_service_url('<url_as_per_region>')\n```\n\n### Username and password\n\n```python\nfrom ibm_watson import DiscoveryV1\nfrom ibm_cloud_sdk_core.authenticators import BasicAuthenticator\n\nauthenticator = BasicAuthenticator('username', 'password')\ndiscovery = DiscoveryV1(version='2019-04-30', authenticator=authenticator)\ndiscovery.set_service_url('<url_as_per_region>')\n```\n\n### No Authentication\n\n```python\nfrom ibm_watson import DiscoveryV1\nfrom ibm_cloud_sdk_core.authenticators import NoAuthAuthenticator\n\nauthenticator = NoAuthAuthenticator()\ndiscovery = DiscoveryV1(version='2019-04-30', authenticator=authenticator)\ndiscovery.set_service_url('<url_as_per_region>')\n```\n\n## Python version\n\nTested on Python 3.9, 3.10, and 3.11.\n\n## Questions\n\nIf you have issues with the APIs or have a question about the Watson services, see [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-watson+python).\n\n## Configuring the http client (Supported from v1.1.0)\n\nTo set client configs like timeout use the `set_http_config()` function and pass it a dictionary of configs. See this [documentation](https://requests.readthedocs.io/en/latest/api/) for more information about the options. All options shown except `method`, `url`, `headers`, `params`, `data`, and `auth` are configurable via `set_http_config()`. For example for a Assistant service instance\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\nauthenticator = IAMAuthenticator('your apikey')\nassistant = AssistantV1(\n version='2021-11-27',\n authenticator=authenticator)\nassistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')\n\nassistant.set_http_config({'timeout': 100})\nresponse = assistant.message(workspace_id=workspace_id, input={\n 'text': 'What\\'s the weather like?'}).get_result()\nprint(json.dumps(response, indent=2))\n```\n\n### Use behind a corporate proxy\n\nTo use the SDK with any proxies you may have they can be set as shown below. For documentation on proxies see [here](https://2.python-requests.org/en/latest/user/advanced/#proxies)\n\nSee this example configuration:\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\nauthenticator = IAMAuthenticator('your apikey')\nassistant = AssistantV1(\n version='2021-11-27',\n authenticator=authenticator)\nassistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')\n\nassistant.set_http_config({'proxies': {\n 'http': 'http://10.10.1.10:3128',\n 'https': 'http://10.10.1.10:1080',\n}})\n```\n\n### Sending custom certificates\n\nTo send custom certificates as a security measure in your request, use the cert property of the HTTPS Agent.\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\nauthenticator = IAMAuthenticator('your apikey')\nassistant = AssistantV1(\n version='2021-11-27',\n authenticator=authenticator)\nassistant.set_service_url('https://api.us-south.assistant.watson.cloud.ibm.com')\n\nassistant.set_http_config({'cert': ('path_to_cert_file','path_to_key_file')})\n```\n\n## Disable SSL certificate verification\n\nFor ICP(IBM Cloud Private), you can disable the SSL certificate verification by:\n\n```python\nservice.set_disable_ssl_verification(True)\n```\n\nOr can set it from extrernal sources. For example set in the environment variable.\n\n```\nexport <service name>_DISABLE_SSL=True\n```\n\n## Setting the service url\n\nTo set the base service to be used when contacting the service\n\n```python\nservice.set_service_url('my_new_service_url')\n```\n\nOr can set it from extrernal sources. For example set in the environment variable.\n\n```\nexport <service name>_URL=\"<your url>\"\n```\n\n## Sending request headers\n\nCustom headers can be passed in any request in the form of a `dict` as:\n\n```python\nheaders = {\n 'Custom-Header': 'custom_value'\n}\n```\n\nFor example, to send a header called `Custom-Header` to a call in Watson Assistant, pass\nthe headers parameter as:\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\nauthenticator = IAMAuthenticator('your apikey')\nassistant = AssistantV1(\n version='2018-07-10',\n authenticator=authenticator)\nassistant.set_service_url('https://gateway.watsonplatform.net/assistant/api')\n\nresponse = assistant.list_workspaces(headers={'Custom-Header': 'custom_value'}).get_result()\n```\n\n## Parsing HTTP response information\n\nIf you would like access to some HTTP response information along with the response model, you can set the `set_detailed_response()` to `True`. Since Python SDK `v2.0`, it is set to `True`\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import IAMAuthenticator\n\nauthenticator = IAMAuthenticator('your apikey')\nassistant = AssistantV1(\n version='2018-07-10',\n authenticator=authenticator)\nassistant.set_service_url('https://gateway.watsonplatform.net/assistant/api')\n\nassistant.set_detailed_response(True)\nresponse = assistant.list_workspaces(headers={'Custom-Header': 'custom_value'}).get_result()\nprint(response)\n```\n\nThis would give an output of `DetailedResponse` having the structure:\n\n```python\n{\n 'result': <response returned by service>,\n 'headers': { <http response headers> },\n 'status_code': <http status code>\n}\n```\n\nYou can use the `get_result()`, `get_headers()` and get_status_code() to return the result, headers and status code respectively.\n\n## Getting the transaction ID\n\nEvery SDK call returns a response with a transaction ID in the `X-Global-Transaction-Id` header. Together the service instance region, this ID helps support teams troubleshoot issues from relevant logs.\n\n### Suceess\n\n```python\nfrom ibm_watson import AssistantV1\n\nservice = AssistantV1(authenticator={my_authenticator})\nresponse_headers = service.my_service_call().get_headers()\nprint(response_headers.get('X-Global-Transaction-Id'))\n```\n\n### Failure\n\n```python\nfrom ibm_watson import AssistantV1, ApiException\n\ntry:\n service = AssistantV1(authenticator={my_authenticator})\n service.my_service_call()\nexcept ApiException as e:\n print(e.global_transaction_id)\n # OR\n print(e.http_response.headers.get('X-Global-Transaction-Id'))\n```\n\nHowever, the transaction ID isn't available when the API doesn't return a response for some reason. In that case, you can set your own transaction ID in the request. For example, replace `<my-unique-transaction-id>` in the following example with a unique transaction ID.\n\n```python\nfrom ibm_watson import AssistantV1\n\nservice = AssistantV1(authenticator={my_authenticator})\nservice.my_service_call(headers={'X-Global-Transaction-Id': '<my-unique-transaction-id>'})\n```\n\n## Using Websockets\n\nThe Text to Speech service supports synthesizing text to spoken audio using web sockets with the `synthesize_using_websocket`. The Speech to Text service supports recognizing speech to text using web sockets with the `recognize_using_websocket`. These methods need a custom callback class to listen to events. Below is an example of `synthesize_using_websocket`. Note: The service accepts one request per connection.\n\n```py\nfrom ibm_watson.websocket import SynthesizeCallback\n\nclass MySynthesizeCallback(SynthesizeCallback):\n def __init__(self):\n SynthesizeCallback.__init__(self)\n\n def on_audio_stream(self, audio_stream):\n return audio_stream\n\n def on_data(self, data):\n return data\n\nmy_callback = MySynthesizeCallback()\nservice.synthesize_using_websocket('I like to pet dogs',\n my_callback,\n accept='audio/wav',\n voice='en-US_AllisonVoice'\n )\n```\n\n## Cloud Pak for Data\n\nIf your service instance is of CP4D, below are two ways of initializing the assistant service.\n\n### 1) Supplying the username, password and authentication url\n\nThe SDK will manage the token for the user\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import CloudPakForDataAuthenticator\n\nauthenticator = CloudPakForDataAuthenticator(\n '<your username>',\n '<your password>',\n '<authentication url>', # should be of the form https://{icp_cluster_host}{instance-id}/api\n disable_ssl_verification=True) # Disable ssl verification for authenticator\n\nassistant = AssistantV1(\n version='<version>',\n authenticator=authenticator)\nassistant.set_service_url('<service url>') # should be of the form https://{icp_cluster_host}/{deployment}/assistant/{instance-id}/api\nassistant.set_disable_ssl_verification(True) # MAKE SURE SSL VERIFICATION IS DISABLED\n```\n\n### 2) Supplying the access token\n\n```python\nfrom ibm_watson import AssistantV1\nfrom ibm_cloud_sdk_core.authenticators import BearerTokenAuthenticator\n\nauthenticator = BearerTokenAuthenticator('your managed access token')\nassistant = AssistantV1(version='<version>',\n authenticator=authenticator)\nassistant.set_service_url('<service url>') # should be of the form https://{icp_cluster_host}/{deployment}/assistant/{instance-id}/api\nassistant.set_disable_ssl_verification(True) # MAKE SURE SSL VERIFICATION IS DISABLED\n```\n\n## Logging\n\n### Enable logging\n\n```python\nimport logging\nlogging.basicConfig(level=logging.DEBUG)\n```\n\nThis would show output of the form:\n\n```\nDEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): iam.cloud.ibm.com:443\nDEBUG:urllib3.connectionpool:https://iam.cloud.ibm.com:443 \"POST /identity/token HTTP/1.1\" 200 1809\nDEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443\nDEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 \"POST /assistant/api/v1/workspaces?version=2018-07-10 HTTP/1.1\" 201 None\nDEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443\nDEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 \"GET /assistant/api/v1/workspaces/883a2a44-eb5f-4b1a-96b0-32a90b475ea8?version=2018-07-10&export=true HTTP/1.1\" 200 None\nDEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): gateway.watsonplatform.net:443\nDEBUG:urllib3.connectionpool:https://gateway.watsonplatform.net:443 \"DELETE /assistant/api/v1/workspaces/883a2a44-eb5f-4b1a-96b0-32a90b475ea8?version=2018-07-10 HTTP/1.1\" 200 28\n```\n\n### Low level request and response dump\n\nTo get low level information of the requests/ responses:\n\n```python\nfrom http.client import HTTPConnection\nHTTPConnection.debuglevel = 1\n```\n\n## Dependencies\n\n- [requests]\n- `python_dateutil` >= 2.5.3\n- [responses] for testing\n- Following for web sockets support in speech to text\n - `websocket-client` 1.1.0\n- `ibm_cloud_sdk_core` >= 3.16.2\n\n## Contributing\n\nSee [CONTRIBUTING.md][contributing].\n\n## License\n\nThis library is licensed under the [Apache 2.0 license][license].\n",
"bugtrack_url": null,
"license": "Apache 2.0",
"summary": "Client library to use the IBM Watson Services",
"version": "8.0.0",
"project_urls": {
"Homepage": "https://github.com/watson-developer-cloud/python-sdk"
},
"split_keywords": [
"language",
"vision",
"question and answer tone_analyzer",
"natural language classifier",
"text to speech",
"language translation",
"language identification",
"concept expansion",
"machine translation",
"personality insights",
"message resonance",
"watson developer cloud",
"wdc",
"watson",
"ibm",
"dialog",
"user modeling",
"tone analyzer",
"speech to text",
"visual recognition"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "2f3f4708bf3f6d369630761fa8c230a588b2b52d2bc65211db874ffd393dff51",
"md5": "5b28099e594258725241e331bcb181fa",
"sha256": "bc1740d22814134d6fda383001a7345b3c87d1ec7372c915ff70a6aaa510973d"
},
"downloads": -1,
"filename": "ibm-watson-8.0.0.tar.gz",
"has_sig": false,
"md5_digest": "5b28099e594258725241e331bcb181fa",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 398263,
"upload_time": "2024-02-26T17:37:50",
"upload_time_iso_8601": "2024-02-26T17:37:50.466755Z",
"url": "https://files.pythonhosted.org/packages/2f/3f/4708bf3f6d369630761fa8c230a588b2b52d2bc65211db874ffd393dff51/ibm-watson-8.0.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-02-26 17:37:50",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "watson-developer-cloud",
"github_project": "python-sdk",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "ibm-watson"
}
JSON
