Skip to content

Commit 70ba43f

Browse files
authored
Update README.md
1 parent fc22a7c commit 70ba43f

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

README.md

+17-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,19 @@
11
[![Build Status](https://travis-ci.org/watsonwork/watsonwork-api-proxy.svg?branch=master)](https://travis-ci.org/watsonwork/watsonwork-api-proxy) [![Greenkeeper badge](https://badges.greenkeeper.io/watsonwork/watsonwork-api-proxy.svg)](https://greenkeeper.io/)
22

3-
# watsonwork-api-proxy
3+
# Watson Work API Proxy
4+
5+
This is a proxy that allows accessing IBM Watson Work APIs with client credentials instead of OAuth access token.
6+
7+
## Basics
8+
9+
IBM Watson Work requires all API calls to include a bearer token. However, for some integration environments it may be problematic to include token calls and token refresh.
10+
11+
This proxy allows making calls to Watson Work APIs with your app's client credentials using Basic authentication. When called, proxy will exchange the credentials for the access token and forward the call to Watson Work.
12+
13+
## Operation
14+
You can deploy the app yourself or use a version deployed already on bluemix under `https://watsonwork-api-proxy.mybluemix.net/`.
15+
16+
In order to make an API call, you just use a proxy hostname and the path of the API you want to call. For example, in order to call `https://watsonwork.ibm.com/graphql`, use `https://watsonwork-api-proxy.mybluemix.net/graphql`, or other hostname for your local deployment.
17+
18+
## Build and test
19+
The build definition includes a simple test that verifies end-to-end proxy operation. The test requires 2 environment variables, `TEST_CLIENT_ID` and `TEST_CLIENT_SECRET` with values matchinge some active Watson Work app.

0 commit comments

Comments
 (0)