Google Android Management API
Browse all Google APIs✓ Official Vendor SpecIdentity AuthDirectory Servicesoauth218 EndpointsREST
For Agents
Define policies, enroll devices, push apps, and issue remote commands on Android Enterprise devices. Useful for agents building or operating an EMM on top of Google's hosted Android management stack.
Use for: Create a new device policy for the marketing team, Generate an enrollment token for a new corporate phone, Lock a lost device and require a new password, Wipe a stolen device remotely
Not supported: Does not handle Android app build uploads, in-app purchases, or consumer device backup — use for enterprise device policy, enrollment, and command management only.
The Android Management API provides remote enterprise management of Android devices and apps. Administrators define policies, enroll devices via enrollment tokens, push apps from managed Google Play, and issue commands such as lock, reboot, and wipe. The API also exposes web apps, web tokens for managed Play iframes, and operation handles for long-running device commands.
Install Jentic One Beta
Connect the Android Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Android Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Android Management API.
Define and update Android device policies
Generate enrollment tokens to add devices to an enterprise
Issue remote commands to lock, reboot, or wipe a device
Push managed apps and configurations to enrolled devices
Generate web tokens for embedding the managed Play iframe
Track long-running device operations through to completion
Use Cases
Patterns agents use Android Management API for, with concrete tasks.
★ Hosted EMM build for SMBs
An ISV builds an Android EMM product on top of Android Management instead of running a self-hosted EMM partner. Policies, enrollment, app distribution, and commands all run through Google's hosted backend, so the ISV ships features faster and offloads infrastructure to Google.
Create policy 'kiosk-v1' with kioskCustomLauncherEnabled true under enterprise enterprises/E-1234, then create an enrollment token referencing that policy.
Lost or stolen device response
When an end user reports a missing device, the help desk issues a lock command and, if not recovered, a remote wipe. Both operations return a long-running operation handle the agent polls until the command lands on the device, providing audit-grade confirmation.
Issue a LOCK command on enterprises/E-1234/devices/D-99 and poll the returned operation under /v1/{+name} until it reports done.
Bulk policy rollout for new device cohort
When a department expands, IT mints a new enrollment token, updates the assigned policy with the relevant Wi-Fi profile and app set, and distributes the QR code to staff. Devices enroll on first boot and immediately apply the policy, replacing manual provisioning.
Patch policy enterprises/E-1234/policies/sales with the corp Wi-Fi profile, then create an enrollment token bound to that policy.
AI agent device operations through Jentic
An AI agent automates ticket triage for a managed mobility help desk. Tickets like 'phone lost' or 'reset device' map to policy patches and command issuance through Jentic, with the agent never holding the underlying service account key.
Read open tickets tagged 'lost-device', issue LOCK followed by RESET_PASSWORD on each affected device, and post the resulting operation IDs back to the ticket.
Key Endpoints
18 endpoints — the android management api provides remote enterprise management of android devices and apps.
METHOD
PATH
DESCRIPTION
GET
/v1/enterprises
List enterprises owned by the caller
POST
/v1/signupUrls
Create a signup URL for a new enterprise
POST
/v1/{+name}:issueCommand
Issue a command (LOCK, RESET_PASSWORD, etc.) on a device
GET
/v1/{+parent}/devices
List devices in an enterprise
GET
/v1/{+parent}/enrollmentTokens
List enrollment tokens
DELETE
/v1/{+name}
Delete a resource (device, policy, token)
GET
/v1/enterprises
List enterprises owned by the caller
POST
/v1/signupUrls
Create a signup URL for a new enterprise
POST
/v1/{+name}:issueCommand
Issue a command (LOCK, RESET_PASSWORD, etc.) on a device
GET
/v1/{+parent}/devices
List devices in an enterprise
GET
/v1/{+parent}/enrollmentTokens
List enrollment tokens
DELETE
/v1/{+name}
Delete a resource (device, policy, token)
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Service account JSON for the Android Management service is stored encrypted in the Jentic vault. Agents execute operations through Jentic and never see the raw key, only short-lived scoped tokens at call time.
Intent-based discovery
Agents search Jentic with phrases like 'lock an android device' or 'create enrollment token' and Jentic returns the matching operation and input schema so the agent does not need the full Android Management reference.
Time to first call
Direct integration: 3-7 days for service account setup, policy modeling, and command polling. Through Jentic: under one hour to start issuing policies, enrollment tokens, and commands.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Android Management API through Jentic.
What authentication does the Android Management API use?
It uses OAuth 2.0, generally with a service account granted access to the enterprise. Through Jentic the service account credentials are vaulted and exchanged for scoped access tokens at execution time.
Can I issue remote lock and wipe commands with this API?
Yes. The devices issueCommand operation under /v1/{+name}:issueCommand accepts LOCK, RESET_PASSWORD, and other command types. It returns a long-running operation that you poll under /v1/{+name} until done.
What are the rate limits for the Android Management API?
Google enforces per-project quotas in Cloud Console rather than fixed per-second limits. Long-running command operations consume quota only at issuance, not while you poll, so polling cadence is not the main constraint.
How do I enroll a device through Jentic?
Search Jentic for 'create android enrollment token', load the schema for enterprises.enrollmentTokens.create, and execute it with the enterprise name and target policyName. Render the returned token as a QR code; the device scans it during setup.
Is the Android Management API free?
The API itself is free. Each enterprise has a quota of devices it can manage, and large fleets may require working with Google to lift quotas.
What is the difference between Android Management and the Google Play EMM API?
Android Management is Google-hosted: policies, enrollment, and commands all run through Google's backend. The Play EMM API is a partner contract surface that lets self-hosted EMMs distribute managed apps. Pick Android Management for new builds; pick Play EMM when integrating with an existing self-hosted EMM.
GET STARTED