Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O SDK da API Android Management (AMAPI) permite que apps específicos
se comuniquem diretamente com o Android Device Policy (ADP). Ele inclui suporte para:
Verifique se o minSdkVersion do app está definido como pelo menos o nível 21 da API.
Adicione as dependências da versão mais recente do SDK da AMAPI ao seu
aplicativo. Na página Notas da versão do SDK da AMAPI, você encontra a versão da biblioteca mais recente disponível e como adicioná-la ao seu aplicativo.
Adicionar elemento de consultas
Se o app segmenta o SDK 30 ou mais recente, o elemento de consultas é necessário no
AndroidManifest.xml para especificar que ele vai interagir com a ADP.
Alguns recursos exigem a criação de um
NotificationReceiverService, e outros
permitem o uso opcional dele. Para usar, defina uma classe que estenda
NotificationReceiverService, adicione-a como um service ao seu
AndroidManifest.xml e verifique se ela foi exportada.
importcom.google.android.managementapi.notification.NotificationReceiverService;...publicfinalclassMyAppNotificationReceiverServiceextendsNotificationReceiverService{@OverrideprotectedvoidsetupInjection(){// This method can be optionally used to inject dependencies at the// beginning of the service lifecycle.}}
Normalmente, o ComponentName da classe que implementa NotificationReceiverService precisa ser transmitido para nós por uma API adequada.
Os detalhes variam de acordo com o recurso em questão, e cada recurso que
precisa disso documenta.
[null,null,["Última atualização 2025-08-28 UTC."],[],[],null,["The [Android Management API (AMAPI) SDK](https://maven.google.com/web/index.html#com.google.android.libraries.enterprise.amapi) enables specific apps to\ncommunicate directly with Android Device Policy (ADP). It includes support for:\n\n- [Local execution of Commands](/android/management/sdk-local-commands)\n- [Migrate devices managed with a custom DPC to AMAPI](/android/management/dpc-migration)\n- [Device Trust from Android Enterprise](/android/management/device-trust-api)\n- New device enrollment flow that also supports adding managed Google Accounts\n- [Manage custom apps with AMAPI](/android/management/manage-custom-apps)\n\nThe following steps must be taken to integrate the AMAPI SDK with your\napplication:\n\n1. [Add the AMAPI SDK library](/android/management/sdk-release-notes#declare_dependencies).\n2. [Add the queries element](#add_queries), if target SDK \\\u003e= 30.\n\n| **Note:** If you are developing an extension app, you will also need to provision the device with an [extensibility policy](/android/management/sdk-local-commands#policy).\n\nPrerequisites\n\n- Verify that your app's `minSdkVersion` is set to at least API level 21.\n- Add the dependencies for the latest version of the AMAPI SDK to your application. You can find the version of the latest available library, and how to add it to your application, in the [AMAPI SDK's release notes](/android/management/sdk-release-notes) page.\n\nAdd queries element\n\nIf your app targets SDK 30 or later, then queries element is needed in the\n`AndroidManifest.xml` to specify that it will interact with ADP. \n\n \u003cqueries\u003e\n \u003cpackage android:name=\"com.google.android.apps.work.clouddpc\" /\u003e\n \u003c/queries\u003e\n\nSee [Package visibility filtering on Android](https://developer.android.com/training/package-visibility) for more information.\n\nImplement a NotificationReceiverService\n\nSome features require creating a\n[`NotificationReceiverService`](/android/management/reference/amapi/com/google/android/managementapi/notification/NotificationReceiverService), and some features\nmake optional use of it. To use it, define a class extending\n`NotificationReceiverService`, add it as a `service` to your\n`AndroidManifest.xml`, and make sure it is exported. \n\n\n import com.google.android.managementapi.notification.NotificationReceiverService;\n\n ...\n\n public final class MyAppNotificationReceiverService extends NotificationReceiverService {\n\n @Override\n protected void setupInjection() {\n // This method can be optionally used to inject dependencies at the\n // beginning of the service lifecycle.\n }\n }\n\nIn your `AndroidManifest.xml`, add \n\n \u003cservice\n android:name = \".MyAppNotificationReceiverService\"\n android:exported = \"true\" /\u003e\n\nTypically the `ComponentName` of your class which implements\n`NotificationReceiverService` needs to be passed to us through a suitable API.\nThe details vary depending on the feature in question, and each feature which\nneeds this documents it."]]