Android Device Provisioning Partner API
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
裝置經銷商可透過這個 API,以程式輔助的方式管理零接觸註冊機制。
服務:androiddeviceprovision.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 個
依據硬體 ID (例如 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 個
列出供應商的客戶。 |
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間: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. |"]]