- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- Try it!
Lists the notification channels that have been created for the project.
HTTP request
GET https://monitoring.googleapis.com/v3/{name}/notificationChannels
Path parameters
Parameters | |
---|---|
name |
Required. The project on which to execute the request. The format is:
This names the container in which to look for the notification channels; it does not name a specific channel. To query a specific channel by REST resource name, use the Authorization requires the following IAM permission on the specified resource
|
Query parameters
Parameters | |
---|---|
filter |
If provided, this field specifies the criteria that must be met by notification channels to be included in the response. For more details, see sorting and filtering. |
orderBy |
A comma-separated list of fields by which to sort the result. Supports the same set of fields as in For more details, see sorting and filtering. |
pageSize |
The maximum number of results to return in a single response. If not set to a positive number, a reasonable value will be chosen by the service. |
pageToken |
If non-empty, |
Request body
The request body must be empty.
Response body
If successful, the response body contains data with the following structure:
The notificationChannels.list
response.
JSON representation | |
---|---|
{
"notificationChannels": [
{
object ( |
Fields | |
---|---|
notificationChannels[] |
The notification channels defined for the specified project. |
nextPageToken |
If not empty, indicates that there may be more results that match the request. Use the value in the |
totalSize |
The total number of notification channels in all pages. This number is only an estimate, and may change in subsequent pages. https://aip.dev/158 |
Authorization Scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/cloud-platform
https://www.googleapis.com/auth/monitoring
https://www.googleapis.com/auth/monitoring.read
For more information, see the Authentication Overview.