Android Device Provisioning Partner API
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
借助此 API,设备转销商可以程序化地管理零触摸注册。
服务:androiddeviceProvisioning.googleapis.com
如要调用此服务,我们建议您使用 Google 提供的客户端库。如果您的应用需要使用您自己的库来调用此服务,则在发出 API 请求时应使用以下信息。
发现文档
发现文档是用于说明和使用 REST API 的机器可读规范。它用于构建客户端库、IDE 插件以及与 Google API 交互的其他工具。一项服务可能会提供多个发现文档。此服务提供了以下发现文档:
服务端点
服务端点是指定 API 服务的网络地址的基本网址。一项服务可能有多个服务端点。此服务具有以下服务端点,下面的所有 URI 都与此服务端点相关:
https://androiddeviceprovisioning.googleapis.com
方法 |
get |
GET /v1/{name=operations/**} 获取长时间运行的操作的最新状态。 |
方法 |
create |
POST /v1/{parent=partners/*}/customers ( )
创建客户以进行零触摸注册。 |
list |
GET /v1/partners/{partnerId}/customers ( )
列出已注册到由 partnerId 参数标识的转销商的客户。 |
方法 |
claim |
POST /v1/partners/{partnerId}/devices:claim ( )
为客户认领设备并将其添加到零触摸注册。 |
claimAsync |
POST /v1/partners/{partnerId}/devices:claimAsync ( )
异步声明客户的一批设备。 |
findByIdentifier |
POST /v1/partners/{partnerId}/devices:findByIdentifier ( )
按硬件标识符(如 IMEI)查找设备。 |
findByOwner |
POST /v1/partners/{partnerId}/devices:findByOwner ( )
查找已为客户领取的设备。 |
get |
GET /v1/{name=partners/*/devices/*} ( )
获取设备。 |
metadata |
POST /v1/partners/{metadataOwnerId}/devices/{deviceId}/metadata ( )
更新与设备关联的转销商元数据。 |
unclaim |
POST /v1/partners/{partnerId}/devices:unclaim ( )
取消对客户设备的声明,并将其从零触摸注册中移除。 |
unclaimAsync |
POST /v1/partners/{partnerId}/devices:unclaimAsync ( )
异步为客户取消认领一批设备。 |
updateMetadataAsync |
POST /v1/partners/{partnerId}/devices:updateMetadataAsync ( )
更新附加到批量设备的转销商元数据。 |
方法 |
list |
GET /v1/{parent=partners/*}/vendors ( )
列出合作伙伴的供应商。 |
方法 |
list |
GET /v1/{parent=partners/*/vendors/*}/customers ( )
列出供应商的客户。 |
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis API empowers device resellers to manage zero-touch enrollment programmatically.\u003c/p\u003e\n"],["\u003cp\u003eThe API's resources include operations, partners' customers, partners' devices, partners' vendors, and partners' vendors' customers, enabling management of various aspects of the enrollment process.\u003c/p\u003e\n"],["\u003cp\u003eThe API service endpoint is \u003ccode\u003ehttps://androiddeviceprovisioning.googleapis.com\u003c/code\u003e, and all resource URIs are relative to this address.\u003c/p\u003e\n"],["\u003cp\u003eThe API supports multiple methods like creating, listing, claiming, unclaiming, and finding devices or customers, all tailored for managing zero-touch enrollment.\u003c/p\u003e\n"],["\u003cp\u003eThis API offers a machine-readable specification for describing REST APIs, for building client libraries and other tools using the provided discovery document.\u003c/p\u003e\n"]]],["This API allows resellers to manage zero-touch enrollment for devices. Key actions include creating and listing customers, claiming and unclaimed devices, and finding devices by identifiers or owner. Resellers can also update device metadata. The API provides asynchronous options for batch device operations. It also allows listing a partner's vendors and a vendor's customers. Operations are available to get the latest state of long-running tasks. The service has a discovery document and a service endpoint.\n"],null,["# Android Device Provisioning Partner API\n\nThis API lets device resellers programmatically manage zero-touch enrollment.\n\n- [REST Resource: v1.operations](#v1.operations)\n- [REST Resource: v1.partners.customers](#v1.partners.customers)\n- [REST Resource: v1.partners.devices](#v1.partners.devices)\n- [REST Resource: v1.partners.vendors](#v1.partners.vendors)\n- [REST Resource: v1.partners.vendors.customers](#v1.partners.vendors.customers)\n\nService: androiddeviceprovisioning.googleapis.com\n-------------------------------------------------\n\nTo call this service, we recommend that you use the Google-provided [client libraries](https://cloud.google.com/apis/docs/client-libraries-explained). If your application needs to use your own libraries to call this service, use the following information when you make the API requests.\n\n### Discovery document\n\nA [Discovery Document](https://developers.google.com/discovery/v1/reference/apis) is a machine-readable specification for describing and consuming REST APIs. It is used to build client libraries, IDE plugins, and other tools that interact with Google APIs. One service may provide multiple discovery documents. This service provides the following discovery document:\n\n- \u003chttps://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1\u003e\n\n### Service endpoint\n\nA [service endpoint](https://cloud.google.com/apis/design/glossary#api_service_endpoint) is a base URL that specifies the network address of an API service. One service might have multiple service endpoints. This service has the following service endpoint and all URIs below are relative to this service endpoint:\n\n- `https://androiddeviceprovisioning.googleapis.com`\n\nREST Resource: [v1.operations](/zero-touch/reference/reseller/rest/v1/operations)\n---------------------------------------------------------------------------------\n\n| Methods ||\n|--------------------------------------------------------------|-----------------------------------------------------------------------------------|\n| [get](/zero-touch/reference/reseller/rest/v1/operations/get) | `GET /v1/{name=operations/**}` Gets the latest state of a long-running operation. |\n\nREST Resource: [v1.partners.customers](/zero-touch/reference/reseller/rest/v1/partners.customers)\n-------------------------------------------------------------------------------------------------\n\n| Methods ||\n|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| [create](/zero-touch/reference/reseller/rest/v1/partners.customers/create) | `POST /v1/{parent=partners/*}/customers` Creates a customer for zero-touch enrollment. |\n| [list](/zero-touch/reference/reseller/rest/v1/partners.customers/list) | `GET /v1/partners/{partnerId}/customers` Lists the customers that are enrolled to the reseller identified by the `partnerId` argument. |\n\nREST Resource: [v1.partners.devices](/zero-touch/reference/reseller/rest/v1/partners.devices)\n---------------------------------------------------------------------------------------------\n\n| Methods ||\n|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| [claim](/zero-touch/reference/reseller/rest/v1/partners.devices/claim) | `POST /v1/partners/{partnerId}/devices:claim` Claims a device for a customer and adds it to zero-touch enrollment. |\n| [claimAsync](/zero-touch/reference/reseller/rest/v1/partners.devices/claimAsync) | `POST /v1/partners/{partnerId}/devices:claimAsync` Claims a batch of devices for a customer asynchronously. |\n| [findByIdentifier](/zero-touch/reference/reseller/rest/v1/partners.devices/findByIdentifier) | `POST /v1/partners/{partnerId}/devices:findByIdentifier` Finds devices by hardware identifiers, such as IMEI. |\n| [findByOwner](/zero-touch/reference/reseller/rest/v1/partners.devices/findByOwner) | `POST /v1/partners/{partnerId}/devices:findByOwner` Finds devices claimed for customers. |\n| [get](/zero-touch/reference/reseller/rest/v1/partners.devices/get) | `GET /v1/{name=partners/*/devices/*}` Gets a device. |\n| [metadata](/zero-touch/reference/reseller/rest/v1/partners.devices/metadata) | `POST /v1/partners/{metadataOwnerId}/devices/{deviceId}/metadata` Updates reseller metadata associated with the device. |\n| [unclaim](/zero-touch/reference/reseller/rest/v1/partners.devices/unclaim) | `POST /v1/partners/{partnerId}/devices:unclaim` Unclaims a device from a customer and removes it from zero-touch enrollment. |\n| [unclaimAsync](/zero-touch/reference/reseller/rest/v1/partners.devices/unclaimAsync) | `POST /v1/partners/{partnerId}/devices:unclaimAsync` Unclaims a batch of devices for a customer asynchronously. |\n| [updateMetadataAsync](/zero-touch/reference/reseller/rest/v1/partners.devices/updateMetadataAsync) | `POST /v1/partners/{partnerId}/devices:updateMetadataAsync` Updates the reseller metadata attached to a batch of devices. |\n\nREST Resource: [v1.partners.vendors](/zero-touch/reference/reseller/rest/v1/partners.vendors)\n---------------------------------------------------------------------------------------------\n\n| Methods ||\n|----------------------------------------------------------------------|-------------------------------------------------------------------------|\n| [list](/zero-touch/reference/reseller/rest/v1/partners.vendors/list) | `GET /v1/{parent=partners/*}/vendors` Lists the vendors of the partner. |\n\nREST Resource: [v1.partners.vendors.customers](/zero-touch/reference/reseller/rest/v1/partners.vendors.customers)\n-----------------------------------------------------------------------------------------------------------------\n\n| Methods ||\n|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|\n| [list](/zero-touch/reference/reseller/rest/v1/partners.vendors.customers/list) | `GET /v1/{parent=partners/*/vendors/*}/customers` Lists the customers of the vendor. |"]]