Google Android Management API

Name: Android Management API
Brand: Android Management API
Availability: InStock

✓ Official Vendor SpecIdentity AuthDirectory Servicesoauth218 Endpoints

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Android Management API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google service account credential is stored once, encrypted, by your own Jentic One instance and exchanged for short-lived scoped access tokens at execution time. The key never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'lock an Android device' or 'create an enrollment token', and Jentic returns the matching Android Management operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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.

Can I limit what my agent is allowed to do with the Android Management API?

Yes. Because you self-host Jentic One, your own rules decide which Android Management operations and credentials the agent may use. Since the API puts the enterprise and device resources in the URL path (for example /v1/{+parent}/devices and /v1/{+name}:issueCommand), you can pin the agent to a single enterprise so it only lists that enterprise's devices and enrollment tokens. You also choose the exact operations it may call, so destructive actions like issueCommand (LOCK, RESET_PASSWORD) or deleting a resource stay off the table unless you explicitly allow them.

Google Android Management API

Connect the Android Management API to your agent

Capabilities

Start building with Android Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs