Module google_androiddeviceprovisioning1::api [−][src]
Structs
Central instance to access all AndroidProvisioningPartner related resource activities
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.
Creates a new configuration. Once created, a customer can apply the configuration to devices.
Deletes an unused configuration. The API call fails if the customer has devices with the configuration applied.
Gets the details of a configuration.
Lists a customer’s configurations.
Updates a configuration’s field values.
Applies a Configuration to the device to register the device for zero-touch enrollment. After applying a configuration to a device, the device automatically provisions itself on first boot, or next factory reset.
Gets the details of a device.
Lists a customer’s devices.
Removes a configuration from device.
Unclaims a device from a customer and removes it from zero-touch enrollment. After removing a device, a customer must contact their reseller to register the device into zero-touch enrollment again.
Lists the DPCs (device policy controllers) that support zero-touch enrollment.
Lists the user’s customer accounts.
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.
A builder providing access to all methods supported on customer resources.
It is not used directly, but through the AndroidProvisioningPartner hub.
Request message for customer to remove the configuration from device.
Request message for customer to unclaim a device.
An Android 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.
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); } The JSON representation for Empty is empty JSON object {}.
Request to find devices.
Response containing found devices.
Request to find devices by customers.
Response containing found devices.
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.
Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.
A builder providing access to all methods supported on operation resources.
It is not used directly, but through the AndroidProvisioningPartner hub.
Identifies one claim request.
Creates a customer for zero-touch enrollment. After the method returns successfully, admin and owner roles can manage devices and EMM configs by calling API methods or using their zero-touch enrollment portal. The customer receives an email that welcomes them to zero-touch enrollment and explains how to sign into the portal.
Lists the customers that are enrolled to the reseller identified by the partnerId argument. This list includes customers that the reseller created and customers that enrolled themselves using the portal.
Claims a batch of devices for a customer asynchronously. Adds the devices to zero-touch enrollment. To learn more, read Long‑running batch operations.
Claims a device for a customer and adds it to zero-touch enrollment. If the device is already claimed by another customer, the call returns an error.
Finds devices by hardware identifiers, such as IMEI.
Finds devices claimed for customers. The results only contain devices registered to the reseller that’s identified by the partnerId argument. The customer’s devices purchased from other resellers don’t appear in the results.
Gets a device.
Updates reseller metadata associated with the device.
Unclaims a batch of devices for a customer asynchronously. Removes the devices from zero-touch enrollment. To learn more, read Long‑running batch operations.
Unclaims a device from a customer and removes it from zero-touch enrollment.
Updates the reseller metadata attached to a batch of devices. This method updates devices asynchronously and returns an Operation that can be used to track progress. Read Long‑running batch operations.
A builder providing access to all methods supported on partner resources.
It is not used directly, but through the AndroidProvisioningPartner hub.
Identifies one unclaim request.
Lists the customers of the vendor.
Lists the vendors of the partner.
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.