Reclama un lote de dispositivos para un cliente de forma asíncrona. Agrega los dispositivos a la inscripción automática. Para obtener más información, consulta Operaciones por lotes de larga duración.
Solicitud HTTP
POST https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:claimAsync
{"deviceIdentifier": {object (DeviceIdentifier)},"sectionType": enum (DeviceProvisioningSectionType),"deviceMetadata": {object (DeviceMetadata)},"preProvisioningToken": string,// Union field customer can be only one of the following:"customerId": string,"googleWorkspaceCustomerId": string// End of list of possible types for union field customer.}
Obligatorio. Los metadatos que se deben adjuntar al dispositivo en el reclamo.
preProvisioningToken
string
Opcional. Solo puede y debe configurarse en dispositivos con ChromeOS.
Campo de unión customer. Obligatorio. El cliente para el que se reclama el dispositivo. Las direcciones (customer) solo pueden ser una de las siguientes opciones:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-07-25 (UTC)"],[[["\u003cp\u003eThis endpoint \u003ccode\u003ePOST https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:claimAsync\u003c/code\u003e enables partners to asynchronously claim a batch of devices for a customer, adding them to zero-touch enrollment.\u003c/p\u003e\n"],["\u003cp\u003eThe request requires a \u003ccode\u003epartnerId\u003c/code\u003e path parameter, which is the reseller partner's ID, and a request body with a list of device claims within the \u003ccode\u003eclaims\u003c/code\u003e field.\u003c/p\u003e\n"],["\u003cp\u003eEach device claim is identified by a \u003ccode\u003ePartnerClaim\u003c/code\u003e object, which contains the \u003ccode\u003edeviceIdentifier\u003c/code\u003e, \u003ccode\u003esectionType\u003c/code\u003e, \u003ccode\u003edeviceMetadata\u003c/code\u003e, and a customer identifier in the form of \u003ccode\u003ecustomerId\u003c/code\u003e or \u003ccode\u003egoogleWorkspaceCustomerId\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePartnerClaim\u003c/code\u003e object optionally includes a \u003ccode\u003epreProvisioningToken\u003c/code\u003e and is required to complete the request.\u003c/p\u003e\n"],["\u003cp\u003eA successful request returns an \u003ccode\u003eOperation\u003c/code\u003e object, indicating that the long-running operation has been initiated.\u003c/p\u003e\n"]]],["This outlines how to claim devices for a customer asynchronously via the Android zero-touch enrollment API. Use a `POST` request to `https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:claimAsync`, providing the required `partnerId`. The request body, structured in JSON, includes a list of device `claims` with each claim containing the `deviceIdentifier`, `sectionType`, `deviceMetadata`, and the required customer's ID (`customerId` or `googleWorkspaceCustomerId`). The `preProvisioningToken` field is required only for ChromeOS devices. The response body contains an `Operation`.\n"],null,[]]
