AI-generated Key Takeaways
-
The goal of this page is to list all telemetry users.
-
The HTTP request uses a GET method with a specific URL structure including a required
parent
parameter. -
Optional query parameters like
filter
,readMask
,pageSize
, andpageToken
can be used to refine the results. -
The request body should be empty, and the response body contains a list of telemetry users and an optional
nextPageToken
. -
Listing telemetry users 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 users.
HTTP request
GET https://chromemanagement.googleapis.com/v1/{parent=customers/*}/telemetry/users
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. Customer id or "my_customer" to use the customer associated to the account making the request. |
Query parameters
Parameters | |
---|---|
filter |
Only include resources that match the filter. Supported filter fields:
|
readMask |
Read mask to specify which fields to return. Supported readMask paths are:
This is a comma-separated list of fully qualified names of fields. Example: |
pageSize |
Maximum number of results to return. Default value is 100. Maximum value is 1000. |
pageToken |
Token to specify next page in the list. |
Request body
The request body must be empty.
Response body
Response message for listing telemetry users for a customer.
If successful, the response body contains data with the following structure:
JSON representation |
---|
{
"telemetryUsers": [
{
object ( |
Fields | |
---|---|
telemetryUsers[] |
Telemetry users returned in the response. |
nextPageToken |
Token to specify next page in the list. |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/chrome.management.telemetry.readonly