Google Play EMM API
Browse all Google APIs✓ Official Vendor SpecDeveloper ToolsPackage Registryoauth277 EndpointsREST
For Agents
Manage the deployment of apps, web apps, and licenses to Android Enterprise devices through an EMM provider. Useful for agents that distribute corporate apps and policies to managed Android fleets.
Use for: Enroll a new enterprise in managed Google Play, Approve a managed Google Play app for distribution, Push a web app shortcut to all corporate devices, Assign a paid app license to a specific user
Not supported: Does not handle device policy enforcement, in-app billing, or app build publishing — use for managed Google Play app distribution and EMM operations only.
The Google Play EMM API lets enterprise mobility management providers deploy, license, and manage apps on Android Enterprise devices. EMM partners use it to enroll enterprises, distribute managed Google Play apps, push web apps, manage app permissions and licenses, and configure managed device policies. The API also covers store layouts, product approvals, service accounts, and notification pulls for near-real-time device state updates.
Install Jentic One Beta
Connect the Google Play EMM API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Play EMM 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 Google Play EMM API.
Enroll, acknowledge, and unenroll enterprises in managed Google Play
Approve managed Google Play apps and assign them to user groups
Push web apps and store layouts to managed Android devices
Manage entitlements and licenses for paid managed apps
Pull notification sets for device, install, and product state changes
Configure managed configurations for individual apps
Use Cases
Patterns agents use Google Play EMM API for, with concrete tasks.
★ Managed app distribution to corporate devices
EMM admins approve apps in managed Google Play, assign them to user groups, and push installs to enrolled devices. The API exposes products, entitlements, installs, and managed configurations so the EMM can keep app state synchronized across the enterprise without manual side-loading.
Approve product app:com.example.crm for enterprise E-1234 and create installs for every device in user group G-789.
Web app shortcuts for the managed Play Store
IT teams publish branded web shortcuts (PWA-style links) into the managed Play Store so end users can launch internal tools without sideloading. The webapps endpoints handle creation, icon upload, and update, and the shortcuts then appear in users' managed Play.
Create a web app titled 'Internal Wiki' pointing to https://wiki.example.com under enterprise E-1234 and assign it to all users.
Notification-driven device state sync
EMM backends call pullNotificationSet on a regular cadence to receive batched events about new device registrations, install completions, and product approvals. This avoids polling individual device endpoints and keeps the EMM's view of the fleet current without burning quota.
Call pullNotificationSet for enterprise E-1234, then acknowledge the returned notification set ID.
AI agent EMM operations through Jentic
An AI agent acting as a Tier-1 EMM admin handles repetitive provisioning tasks (enrolling new users, approving requested apps, fixing failed installs) by searching Jentic for the operation, loading the schema, and executing the call. The agent never needs the underlying service account key.
Find every install in state 'installError' for enterprise E-1234 and re-issue the install command for each one.
Key Endpoints
77 endpoints — the google play emm api lets enterprise mobility management providers deploy, license, and manage apps on android enterprise devices.
METHOD
PATH
DESCRIPTION
GET
/androidenterprise/v1/enterprises
List enrolled enterprises
POST
/androidenterprise/v1/enterprises/enroll
Enroll a new enterprise
POST
/androidenterprise/v1/enterprises/pullNotificationSet
Pull batched device and install notifications
POST
/androidenterprise/v1/enterprises/acknowledgeNotificationSet
Acknowledge a pulled notification set
GET
/androidenterprise/v1/enterprises/{enterpriseId}
Get an enterprise by ID
POST
/androidenterprise/v1/enterprises/signupUrl
Generate a managed Play signup URL
GET
/androidenterprise/v1/enterprises
List enrolled enterprises
POST
/androidenterprise/v1/enterprises/enroll
Enroll a new enterprise
POST
/androidenterprise/v1/enterprises/pullNotificationSet
Pull batched device and install notifications
POST
/androidenterprise/v1/enterprises/acknowledgeNotificationSet
Acknowledge a pulled notification set
GET
/androidenterprise/v1/enterprises/{enterpriseId}
Get an enterprise by ID
POST
/androidenterprise/v1/enterprises/signupUrl
Generate a managed Play signup URL
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
EMM service account credentials are stored encrypted in the Jentic vault. Agents call operations through Jentic and receive a scoped access token without the raw service account JSON ever entering the agent context.
Intent-based discovery
Agents search Jentic with phrases like 'approve managed google play app' or 'pull device notifications' and Jentic returns the matching operation and its input schema so the agent does not need to navigate the EMM API reference.
Time to first call
Direct integration: 5-10 days to set up the EMM partner workflow, service account, notification polling, and error recovery. Through Jentic: under one hour to start running approve, install, and notification-pull operations.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Google Play EMM API through Jentic.
What authentication does the Google Play EMM API use?
It uses OAuth 2.0, typically with a service account that has been authorized for the enterprise. Through Jentic the service account JSON is stored encrypted in the vault and exchanged for a scoped access token at call time.
Can I push web app shortcuts with this API?
Yes. The webapps endpoints under /androidenterprise/v1/enterprises/{enterpriseId}/webApps let you create, list, update, and delete web app shortcuts that appear in the managed Play Store.
What are the rate limits for the Google Play EMM API?
Google enforces per-project quotas in the Cloud Console. Notification-based endpoints (pullNotificationSet) are designed for steady polling and have higher effective throughput than per-device polling, so prefer them for fleet-wide state sync.
How do I approve and assign a managed Google Play app through Jentic?
Search Jentic for 'approve managed google play app', load the schema for products.approve, and execute it with the enterpriseId and productId. Then call entitlements.update or installs.update through Jentic to assign the app to users or devices.
Is the Google Play EMM API free?
The API itself is free for approved EMM partners. App licensing costs (for paid apps) flow through entitlements, not the API surface. EMM partner approval is required before the endpoints become callable.
How do I detect failed installs across the enterprise?
Pull a notification set with installs.pullNotificationSet, filter for installs whose installState indicates failure, and re-issue installs.update for those device and product pairs.
GET STARTED