2024-11-21
▼ ▲ chromemanagement.customers.profiles.get
Flat Path : v1/customers/{customersId}/profiles/{profilesId}
Parameter Order : name
Parameters :
name
Required : Yes
Pattern : ^customers/[^/]+/profiles/[^/]+$
Location : path
Type : string
Description : Required. Format: customers/{customer_id}/profiles/{profile_permanent_id}
Path : v1/{+name}
HTTP Method : GET
Description : Gets a Chrome browser profile with customer ID and profile permanent ID.
▼ ▲ chromemanagement.customers.profiles.delete
Parameter Order : name
Parameters :
name
Pattern : ^customers/[^/]+/profiles/[^/]+$
Description : Required. Format: customers/{customer_id}/profiles/{profile_permanent_id}
Type : string
Location : path
Required : Yes
Description : Deletes the data collected from a Chrome browser profile.
HTTP Method : DELETE
Path : v1/{+name}
Flat Path : v1/customers/{customersId}/profiles/{profilesId}
▼ ▲ chromemanagement.customers.profiles.list
Path : v1/{+parent}/profiles
Parameter Order : parent
HTTP Method : GET
Parameters :
filter
Type : string
Description : Optional. The filter used to filter profiles. The following fields can be used in the filter: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state - ouId Any of the above fields can be used to specify a filter, and filtering by multiple fields is supported with AND operator. String type fields and enum type fields support '=' and '!=' operators. The integer type and the timestamp type fields support '=', '!=', '<', '>', '<=' and '>=' operators. Timestamps expect an RFC-3339 formatted string (e.g. 2012-04-21T11:30:00-04:00). Wildcard '*' can be used with a string type field filter. In addition, string literal filtering is also supported, for example, 'ABC' as a filter maps to a filter that checks if any of the filterable string type fields contains 'ABC'. Organization unit number can be used as a filtering criteria here by specifying 'ouId = ${your_org_unit_id}', please note that only single OU ID matching is supported.
Location : query
orderBy
Description : Optional. The fields used to specify the ordering of the results. The supported fields are: - profile_id - display_name - user_email - last_activity_time - last_policy_sync_time - last_status_report_time - first_enrollment_time - os_platform_type - os_version - browser_version - browser_channel - policy_count - extension_count - identity_provider - affiliation_state By default, sorting is in ascending order, to specify descending order for a field, a suffix " desc" should be added to the field name. The default ordering is the descending order of last_status_report_time.
Type : string
Location : query
pageSize
Format : int32
Location : query
Description : Optional. The maximum number of profiles to return. The default page size is 100 if page_size is unspecified, and the maximum page size allowed is 200.
Type : integer
parent
Location : path
Pattern : ^customers/[^/]+$
Type : string
Description : Required. Format: customers/{customer_id}
Required : Yes
pageToken
Description : Optional. The page token used to retrieve a specific page of the listing request.
Type : string
Location : query
Description : Lists Chrome browser profiles of a customer based on the given search and sorting criteria.
Flat Path : v1/customers/{customersId}/profiles