Android management API | Google Developers – ABOUT MAG 2020

The Android management API is available as part of Android Enterprise,
an initiative that provides developers with tools to create solutions for organizations
to manage your Android device fleets. The program is aimed at companies
mobility management providers (EMMs). To deploy a production solution
using the Android Management API, EMMs need to follow the steps outlined in
Unleash your solution.

You can use the Android Management API to support the work
profile
, fully managed device,
and dedicated device solution sets.

see the Quick guide to try out the API
under standard usage limits.


How it works

The Android Management API supports complete enterprise mobility management
lifecycle, from initial customer enrollment to device configuration and management.

Android Management overview.

As an EMM developer, you provide your customers with a local or cloud-based
EMM console. On your console, your customers generate device registration tokens
and create management policies. They use tokens to register devices and apply
management policies for registered devices.

On the back end, your console uses the Android management API to create
enrollment tokens, policies and other management features. During registration,
each device installs the companion API application,
Android device policy.
When policies are linked to a device in the API, the Android Device Policy automatically
enforces policy settings on the device.


API features

This section describes the main features used in the Android management API.

Enterprises

THE enterprises resource
usually represents a single organization. You create one
development
as part of an online installation flow that your
customers use to link their organization to their EMM solution. Policies,
enrollment tokens and devices belong to a company.

Policies

The Android management API follows a policy-driven model. AN
policies

The resource contains a group of device and application management settings that govern the
behavior of a device. The scope and flexibility of the configurations supported in
policies allow you to configure devices for a variety of different use
cases
.

Watch Create a policy For more informations.

Subscription tokens

You use enrollmentTokens

link devices to a company – a process called registration and provisioning.
Enrollment tokens can optionally contain extra details (for example, corporate WiFi credentials),
an policyName connected to a policies resource and a user account identifier.

After creating a subscription token, you
can pass the token to a device using one of several provisioning
methods
. Gadgets
install the Android Device Policy as part of the provisioning process. If one
policyName is specified in the registration token, the policy will be
applied immediately after provisioning is complete.

The Android Management API simplifies user management – you can register a device
with or without specifying a user in the sign-up token.

  • If you do not specify a user, a new user is created automatically.
  • If you specify an existing user, it will be associated with
    the device. You can associate a user with up to 10 devices.

Watch Provision a device for more
training.

Gadgets

AN devices

The resource is created when a device is successfully registered. The resource
contains read-only details about a device, including its associated user,
policy and management mode.

Device management is done through policy, but you can use
enterprises.devices.issueCommand

lock, reset, or reset the password on a device. To clean a device, call
enterprises.devices.delete.


start

Test the API – use Quick guide for
set up a device in minutes. Make sure you understand the necessary steps to
release your solution in a production
before using the developer guide and API
reference
on this site to create your solution.

Paula Fonseca