Android Management API는 개발자에게 조직에서 Android 기기 풀을 관리하기 위한 솔루션을 빌드하는 도구를 제공하는 이니셔티브인 Android Enterprise의 일부로 제공됩니다. 이 프로그램은 엔터프라이즈 모바일 관리(EMM) 제공업체를 대상으로 합니다. 받는사람
Android Management API를 사용하는 프로덕션 솔루션을 배포할 때 EMM은
솔루션을 참고하세요.
Android Management API는 초기 고객 등록부터 기기 설정 및 관리에 이르기까지 전체 엔터프라이즈 모바일 관리 수명 주기를 지원합니다.
EMM 개발자는 고객에게 온프레미스 또는 클라우드 기반 EMM 콘솔을 제공합니다. 고객이 콘솔에서 기기 등록 토큰을 생성합니다.
관리 정책을 만들 수 있습니다 토큰을 사용하여 기기를 등록하고
관리 정책을 적용할 수 있습니다.
백엔드에서는 콘솔이 Android Management API를 사용하여
등록 토큰, 정책, 기타 관리 리소스입니다. 등록하는 동안 각 기기에는 API의 호환 앱인 Android Device Policy가 설치됩니다.
API에서 정책이 기기에 연결되면 Android Device Policy가 기기에서 정책 설정을 자동으로 시행합니다.
API 리소스
이 섹션에서는 Android Management API에서 사용되는 기본 리소스를 설명합니다.
엔터프라이즈
enterprises 리소스는 일반적으로 단일 조직을 나타냅니다. 고객이 조직을 EMM 솔루션과 결합하는 데 사용하는 온라인 설정 흐름의 일부로 기업을 만듭니다. 정책, 등록 토큰, 기기는 기업에 속합니다.
정책
Android Management API는 정책 기반 모델을 따릅니다. policies 리소스에는 기기의 동작을 제어하는 기기 및 앱 관리 설정 그룹이 포함되어 있습니다. 지원되는 설정의 범위와 유연성
policies을(를) 사용하면 기기를 다양한 용도로 설정할 수 있습니다.
사례
enrollmentTokens를 사용하여 기기를 엔터프라이즈에 바인딩합니다. 이를 등록 및 프로비저닝이라고 합니다.
등록 토큰은 선택적으로 추가 세부 정보 (예: 회사 Wi-Fi 사용자 인증 정보)를 포함할 수 있습니다.
, policies 리소스에 연결된 policyName, 사용자 계정 식별자가 포함됩니다.
등록 토큰을 만든 후 여러 프로비저닝 방법 중 하나를 사용하여 기기에 토큰을 전달할 수 있습니다. 기기는 프로비저닝 프로세스의 일부로 Android Device Policy를 설치합니다. 만약
policyName가 등록 토큰에 지정된 경우 정책이
즉시 적용됩니다.
Android Management API를 사용하면 사용자 관리가 간소화됩니다. 등록 토큰에 사용자를 지정하거나 지정하지 않고 기기를 등록할 수 있습니다.
사용자를 지정하지 않으면 신규 사용자가 자동으로 생성됩니다.
기존 사용자를 지정하면 기존 사용자가
있습니다. 한 명의 기기를 최대 10대의 기기에 연결할 수 있습니다.
[[["이해하기 쉬움","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"]],["최종 업데이트: 2025-07-26(UTC)"],[[["\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."]]
