Google Play EMM API
Browse all Google APIs38
AI ReadinessNon-Ready (F)38/100
Official vendor OpenAPI document · agent-readyDeveloper 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fandroidenterprise" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fandroidenterprise" | 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Google Play EMM API
- Non-Ready (F)38/100
51
Foundational Compliance56
Developer Experience & Jentic Compatibility16
AI-Readiness & Agent Experience90
Agent Usability63
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
51
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
82%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
21%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
16
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
66%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
90
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
90%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Google Play EMM API by hand means setting up Google OAuth 2.0 from an EMM service account, minting short-lived scoped access tokens, and pointing calls at the androidenterprise.googleapis.com host. Through Jentic you install once, import the Google Play EMM API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
The EMM API puts the enterprise id in the URL path (/androidenterprise/v1/enterprises/{enterpriseId}), so a rule can pin your agent to one enterprise: it can read that enterprise and nothing else. You choose the operations it may call, so actions like enroll, pullNotificationSet, or acknowledgeNotificationSet are not included unless you add them.
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 service account JSON never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'approve a managed Google Play app' or 'pull device notifications', and Jentic returns the matching EMM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
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.
Can I limit what my agent is allowed to do with the Google Play EMM API?
Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because the EMM API carries the enterprise id in the URL path (/androidenterprise/v1/enterprises/{enterpriseId}), a rule can pin the agent to a single enterprise, and you choose exactly which operations it may call. That means read-only tasks like listing enterprises or pulling notification sets can be allowed while state-changing calls such as products.approve, installs.update, or acknowledgeNotificationSet stay excluded until you add them.
GET STARTED