View Source API Reference google_api_android_device_provisioning v0.19.0

API client metadata for GoogleApi.AndroidDeviceProvisioning.V1.

API calls for all endpoints tagged Customers.

API calls for all endpoints tagged Operations.

API calls for all endpoints tagged Partners.

Handle Tesla connections for GoogleApi.AndroidDeviceProvisioning.V1.

Request message to claim a device on behalf of a customer.

Response message containing device id of the claim.

Request to claim devices asynchronously in batch. Claiming a device adds the device to zero-touch enrollment and shows the device in the customer's view of the portal.

A reseller, vendor, or customer in the zero-touch reseller and customer APIs.

A configuration collects the provisioning options for Android devices. Each configuration combines the following: The EMM device policy controller (DPC) installed on the devices. EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that's applied to any new devices the organization purchases.

Request message to create a customer.

Request message for customer to assign a configuration to device.

Response message of customer's listing configuration.

Response message for listing my customers.

Response message of customer's liting devices.

Response message of customer's listing DPCs.

Request message for customer to remove the configuration from device.

Request message for customer to unclaim a device.

An Android or Chrome OS device registered for zero-touch enrollment.

A record of a device claimed by a reseller for a customer. Devices claimed for zero-touch enrollment have a claim with the type SECTION_TYPE_ZERO_TOUCH. To learn more, read Claim devices for customers.

Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read Identifiers.

Metadata entries that can be attached to a Device. To learn more, read Device metadata.

A DeviceReference is an API abstraction that lets you supply a device argument to a method using one of the following identifier types: A numeric API resource ID. Real-world hardware IDs, such as IMEI number, belonging to the manufactured device. Methods that operate on devices take a DeviceReference as a parameter type because it's more flexible for the caller. To learn more about device identifiers, read Identifiers.

Tracks the status of a long-running operation to asynchronously update a batch of reseller metadata attached to devices. To learn more, read Long‑running batch operations.

Tracks the status of a long-running operation to claim, unclaim, or attach metadata to devices. To learn more, read Long‑running batch operations.

An EMM's DPC (device policy controller). Zero-touch enrollment installs a DPC (listed in the Configuration) on a device to maintain the customer's mobile policies. All the DPCs listed by the API support zero-touch enrollment and are available in Google Play.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Request to find devices.

Response containing found devices.

Request to find devices by customers.

Response containing found devices.

Request to get a device's SIM lock status.

Response containing a device's SimLock state.

A Google Workspace customer.

Response message of all customers related to this partner.

Response message to list customers of the vendor.

Response message to list vendors of the partner.

This resource represents a long-running operation that is the result of a network API call.

A task for each device in the operation. Corresponds to each device change in the request.

Identifies one claim request.

Identifies one unclaim request.

Captures the processing status for each device in the operation.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Request message to unclaim a device.

Request to unclaim devices asynchronously in batch.

Request to update device metadata in batch.

Request to set metadata for a device.

Identifies metadata updates to one device.