{"deviceMetadata": {object (DeviceMetadata)},// Union field device can be only one of the following:"deviceIdentifier": {object (DeviceIdentifier)},"deviceId": string// End of list of possible types for union field device.}
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2024-08-29 (世界標準時間)。"],[[["This page details how to asynchronously update reseller metadata for a batch of devices using the Android Device Provisioning Partner API."],["The `POST` request is made to a specific URL with a required `partnerId` in the path, using gRPC Transcoding syntax."],["The request body must include a JSON object that specifies the list of metadata updates to be applied using the `UpdateMetadataArguments` format."],["Each `UpdateMetadataArguments` entry must include the `deviceMetadata` to be updated, as well as a device identifier, whether through a `deviceIdentifier` object or a `deviceId` string."],["The request requires the `https://www.googleapis.com/auth/androidworkprovisioning` OAuth scope for authorization, and a successful response returns an `Operation` instance to monitor the progress."]]],["This describes an asynchronous API method for updating reseller metadata on multiple devices. It uses a `POST` request to `https://androiddeviceprovisioning.googleapis.com/v1/partners/{partnerId}/devices:updateMetadataAsync`, requiring a `partnerId` path parameter. The request body needs an array of `updates`, each with device-specific metadata, identified by either `deviceIdentifier` or `deviceId`. The `Operation` object tracks progress for these metadata modifications, which requires the `https://www.googleapis.com/auth/androidworkprovisioning` authorization scope.\n"]]