PUT /v1/accessKeys/{id}
Updates the properties of existing accessKey by accessId. It can be used to enable or disable the access key and to update the corsHeaders list.
Servers
- https://api.au.sumologic.com/api/
- https://api.ca.sumologic.com/api/
- https://api.de.sumologic.com/api/
- https://api.eu.sumologic.com/api/
- https://api.fed.sumologic.com/api/
- https://api.jp.sumologic.com/api/
- https://api.kr.sumologic.com/api/
- https://api.in.sumologic.com/api/
- https://api.sumologic.com/api/
- https://api.us2.sumologic.com/api/
Path parameters
Name | Type | Required | Description |
---|---|---|---|
id |
String | Yes |
The accessId of the access key to update. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
scopes[] |
Array | No |
Scopes assigned to the key. Alerting
Data Management
Logs
Metrics
Reliability Management
Security
UserManagement
|
disabled |
Boolean | Yes |
Indicates whether the access key is disabled or not. |
corsHeaders[] |
Array | No |
An array of domains for which the access key is valid. Whether Sumo Logic accepts or rejects an API request depends on whether it contains an ORIGIN header and the entries in the allowlist. Sumo Logic will reject:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.