POST /v1/healthEvents/resources
Get a list of all the unresolved events in your account that belong to the supplied resource identifiers.
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/
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
limit |
Integer | No |
Limit the number of health events returned in the response. The number of health events returned may be less than the Default value: 100 |
token |
String | No |
Continuation token to get the next page of results. A page object with the next continuation token is returned in the response body. Subsequent GET requests should specify the continuation token to get the next page of results. |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
data[] |
Array | Yes |
A list of the resources. |
data[].id |
String | Yes |
The unique identifier of the resource. |
data[].name |
String | No |
The name of the resource. Default value: "Unknown" |
data[].type |
String | Yes |
-> Resource type. Supported types are - |
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.