Skip to content

Commit 01d44ac

Browse files
committed
docs(readme): remove documentation for old visrec 'apikey'
1 parent 50971c0 commit 01d44ac

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

README.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,6 @@ Watson services are migrating to token-based Identity and Access Management (IAM
8484

8585
- With some service instances, you authenticate to the API by using **[IAM](#iam)**.
8686
- In other instances, you authenticate by providing the **[username and password](#username-and-password)** for the service instance.
87-
- Visual Recognition uses a form of [API key](#api-key) only with instances created before May 23, 2018. Newer instances of Visual Recognition use [IAM](#iam).
8887

8988
### Getting credentials
9089
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:
@@ -148,19 +147,6 @@ var discovery = new DiscoveryV1({
148147
});
149148
```
150149

151-
### API key
152-
153-
**Important**: This type of authentication works only with Visual Recognition instances created before May 23, 2018. Newer instances of Visual Recognition use [IAM](#iam).
154-
155-
```javascript
156-
var VisualRecognitionV3 = require('watson-developer-cloud/visual-recognition/v3');
157-
158-
var visualRecognition = new VisualRecognitionV3({
159-
version: '{version}',
160-
api_key: '{api_key}'
161-
});
162-
```
163-
164150
### Sending request headers
165151

166152
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.

0 commit comments

Comments
 (0)