You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-14Lines changed: 0 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,6 @@ Watson services are migrating to token-based Identity and Access Management (IAM
84
84
85
85
- With some service instances, you authenticate to the API by using **[IAM](#iam)**.
86
86
- 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).
88
87
89
88
### Getting credentials
90
89
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({
148
147
});
149
148
```
150
149
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 =newVisualRecognitionV3({
159
-
version:'{version}',
160
-
api_key:'{api_key}'
161
-
});
162
-
```
163
-
164
150
### Sending request headers
165
151
166
152
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