AI-generated Key Takeaways
-
Use a GET request with the specified URL pattern to list telemetry notification configs.
-
The only required path parameter is
parent
, which identifies the customer. -
Optional query parameters include
pageSize
for controlling the number of results andpageToken
for pagination. -
The request body should be empty.
-
The response body contains a list of
telemetryNotificationConfigs
and an optionalnextPageToken
for pagination. -
Listing requires the
https://www.googleapis.com/auth/chrome.management.telemetry.readonly
authorization scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
List all telemetry notification configs.
HTTP request
GET https://chromemanagement.googleapis.com/v1/{parent=customers/*}/telemetry/notificationConfigs
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. The parent which owns the notification configs. |
Query parameters
Parameters | |
---|---|
pageSize |
The maximum number of notification configs to return. The service may return fewer than this value. If unspecified, at most 100 notification configs will be returned. The maximum value is 100; values above 100 will be coerced to 100. |
pageToken |
A page token, received from a previous When paginating, all other parameters provided to |
Request body
The request body must be empty.
Response body
Response message for listing notification configs for a customer.
If successful, the response body contains data with the following structure:
JSON representation |
---|
{
"telemetryNotificationConfigs": [
{
object ( |
Fields | |
---|---|
telemetryNotificationConfigs[] |
The telemetry notification configs from the specified customer. |
nextPageToken |
A token, which can be sent as |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/chrome.management.telemetry.readonly