AI-generated Key Takeaways
-
This endpoint claims a device for a customer, adding it to zero-touch enrollment, and returns an error if the device is already claimed by another customer.
-
The HTTP request to claim a device is a POST request to
https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:claim, requiring the reseller partner's ID in the path parameters. -
The request body must include the
deviceIdentifier,sectionType, and the customer's ID (customerIdorgoogleWorkspaceCustomerId), along with optional fields such asdeviceMetadataandpreProvisioningTokenfor Chrome OS devices. -
A successful response contains the
deviceIdof the claimed device and its resource name in the formatpartners/[PARTNER_ID]/devices/[DEVICE_ID]. -
This action requires the OAuth scope
https://www.googleapis.com/auth/androidworkprovisioningfor authorization.
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.
HTTP request
POST https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:claim
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
partnerId |
Required. The ID of the reseller partner. |
Request body
The request body contains data with the following structure:
| JSON representation |
|---|
{ "deviceIdentifier": { object ( |
| Fields | |
|---|---|
deviceIdentifier |
Required. Required. The device identifier of the device to claim. |
sectionType |
Required. The section type of the device's provisioning record. |
deviceMetadata |
Optional. The metadata to attach to the device. |
preProvisioningToken |
Optional. Must and can only be set for Chrome OS devices. |
Union field customer. Required. The customer for whom the device is being claimed. customer can be only one of the following: |
|
customerId |
The ID of the customer for whom the device is being claimed. |
googleWorkspaceCustomerId |
The Google Workspace customer ID. |
Response body
If successful, the response body contains data with the following structure:
Response message containing device id of the claim.
| JSON representation |
|---|
{ "deviceId": string, "deviceName": string } |
| Fields | |
|---|---|
deviceId |
The device ID of the claimed device. |
deviceName |
The resource name of the device in the format |
Authorization Scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/androidworkprovisioning
For more information, see the OAuth 2.0 Overview.