[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eThe Android Management API, part of Android Enterprise, enables EMMs to manage Android devices within organizations.\u003c/p\u003e\n"],["\u003cp\u003eEMMs utilize the API to generate enrollment tokens, establish policies, and manage devices throughout their lifecycle.\u003c/p\u003e\n"],["\u003cp\u003eDevices enrolled using the API are managed through policies enforced by the Android Device Policy app.\u003c/p\u003e\n"],["\u003cp\u003eKey resources within the API include \u003ccode\u003eenterprises\u003c/code\u003e, \u003ccode\u003epolicies\u003c/code\u003e, \u003ccode\u003eenrollmentTokens\u003c/code\u003e, and \u003ccode\u003edevices\u003c/code\u003e, offering comprehensive device management capabilities.\u003c/p\u003e\n"],["\u003cp\u003eA quickstart guide is available for initial API exploration, while detailed documentation aids in building production-ready EMM solutions.\u003c/p\u003e\n"]]],["The Android Management API allows enterprise mobility management (EMM) providers to manage Android device fleets. EMMs use their console to create enrollment tokens and management policies. Devices are enrolled using these tokens, installing the Android Device Policy app to enforce policies. Key actions include creating `enterprises`, `policies`, and `enrollmentTokens`. `devices` resources are created upon successful enrollment. Device management involves applying policies, and using commands to lock, reboot, or reset passwords, while deletion will wipe the device.\n"],null,["# Android Management API\n\n| **Note:** If you use the [Google Play EMM API](/android/work/play/emm-api), see the [guide for existing EMM partners](/android/management/existing-emms).\n\nThe Android Management API is available as part of [Android\nEnterprise](/android/work), an initiative providing developers with tools to\nbuild solutions for organizations to manage their Android device fleets. The\nprogram is intended for enterprise mobility management providers (EMMs). To\ndeploy a production solution that uses the Android Management API, EMMs need to\nfollow the steps outlined in [Release your\nsolution](/android/work/release-solution).\n\nYou can use the Android Management API to support the\n[work profile on personally-owned device](/android/work/requirements/work-profile),\n[work profile on company-owned device](/android/work/requirements/work-profile-corporate),\n[fully managed device](/android/work/requirements/fully-managed-device), and\n[dedicated device](/android/work/requirements/dedicated-device) solution sets.\n\nSee the [Quickstart guide](/android/management/quickstart) to try out the API.\n\n*** ** * ** ***\n\nHow it works\n------------\n\nThe Android Management API supports the full enterprise mobility management\nlifecycle, from initial customer enrollment to setting up and managing devices.\n\nAs an EMM developer, you supply your customers with an on-premise or cloud-based\nEMM console. In your console, your customers generate device enrollment tokens\nand create management policies. They use the tokens to enroll devices and apply\nmanagement policies to the devices they enrolled.\n\nIn the backend, your console uses the Android Management API to create\nenrollment tokens, policies, and other management resources. During enrollment,\neach device installs the API's companion app,\n[Android Device Policy](https://play.google.com/store/apps/details?id=com.google.android.apps.work.clouddpc).\nWhen policies are linked to a device in the API, Android Device Policy automatically\nenforces the policy settings on the device.\n| **Note:** Android Device Policy is the **only** device policy controller compatible with Android Management API.\n\n*** ** * ** ***\n\nAPI resources\n-------------\n\nThis section describes the primary resources used in the Android Management API.\n\n### Enterprises\n\nAn [`enterprises`](/android/management/reference/rest/v1/enterprises) resource\ntypically represents a single organization. You [create an\nenterprise](/android/management/create-enterprise) as part of an online setup flow that your\ncustomers use to bind their organization with your EMM solution. Policies,\nenrollment tokens, and devices belong to an enterprise.\n\n### Policies\n\nThe Android Management API follows a policy-driven model. A\n[`policies`](/android/management/reference/rest/v1/enterprises.policies)\nresource contains a group of device and app management settings that govern the\nbehavior of a device. The range and flexibility of the settings supported in\n`policies` allow you to set up devices for a variety of different [use\ncases](/android/work/overview#android_devices_enterprise_use_cases).\n\nSee [Create a policy](/android/management/create-policy) for more information.\n\n### Enrollment tokens\n\nYou use [`enrollmentTokens`](/android/management/reference/rest/v1/enterprises.enrollmentTokens)\nto bind devices to an enterprise---a process called enrollment and provisioning.\nEnrollment tokens can optionally contain extra details (e.g. corporate WiFi credentials)\n, a `policyName` linked to a `policies` resource, and a user account identifier.\n\nAfter [creating an enrollment token](/android/management/provision-device), you\ncan pass the token to a device using one of several different [provisioning\nmethods](/android/management/provision-device#provisioning_methods). Devices\ninstall Android Device Policy as part of the provisioning process. If a\n`policyName` is specified in the enrollment token, then the policy will be\napplied immediately after provisioning is complete.\n\nThe Android Management API simplifies user management---you can enroll a device\nwith or without specifying a user in the enrollment token.\n\n- If you don't specify a user, a new user will be created automatically.\n- If you specify an existing user, the existing user will be associated with the device. You can associate a user with up to 10 devices.\n\nSee [Provision a device](/android/management/provision-device) for more\ninformation.\n\n### Devices\n\nA [`devices`](/android/management/reference/rest/v1/enterprises.devices)\nresource is created when a device is successfully enrolled. The resource\ncontains read-only details about a device, including its associated user,\npolicy, and management mode.\n\nDevice management is carried out through policy, but you can use\n[`enterprises.devices.issueCommand`](/android/management/reference/rest/v1/enterprises.devices/issueCommand)\nto lock, reboot, or reset the password on a device. To wipe a device, call\n[`enterprises.devices.delete`](/android/management/reference/rest/v1/enterprises.devices/delete)\n.\n\n*** ** * ** ***\n\nGet started\n-----------\n\nTest out the API---use the [Quickstart guide](/android/management/quickstart) to\nset up a device in minutes. Ensure that you understand the steps required to\n[release your solution](/android/work/release-solution) in a production\nenvironment before using the developer's guide and [API\nreference](/android/management/reference/rest) on this site to build your\nsolution."]]
