Google Android Device Provisioning Partner API
Browse all Google APIs40
AI ReadinessFoundational (D-)40/100
Official vendor OpenAPI document · agent-readyIdentity AuthDirectory Servicesoauth224 EndpointsREST
For Agents
Claim, configure, and manage Android zero-touch enrollment devices on behalf of resellers, customers, and EMMs. Useful for agents that need to onboard fleets of corporate Android phones or tablets.
Use for: Claim a batch of Android devices for a new customer, Find a device by IMEI before it ships to the end user, List all customers linked to my reseller account, Apply a zero-touch configuration to a corporate phone
Not supported: Does not handle ongoing device policy, app deployment, or end-user account management - use for zero-touch reseller and customer device claiming only.
The Android Device Provisioning Partner API automates Android zero-touch enrollment for device resellers, enterprise customers, and EMM providers. Resellers use it to claim devices for customers so they can self-deploy, and customers can list, configure, and unclaim corporate-owned Android devices at scale. The API supports synchronous and asynchronous device claim operations, configuration management, and customer linkage so that thousands of devices can be staged before they are unboxed.
Install Jentic One Beta
Connect the Android Device Provisioning Partner API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Android Device Provisioning Partner 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%2Fandroiddeviceprovisioning" | 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%2Fandroiddeviceprovisioning" | 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 Device Provisioning Partner API.
Claim Android devices to a customer for zero-touch enrollment
Find devices by hardware identifier (IMEI, MEID, serial) before shipment
Apply or remove a zero-touch configuration on a claimed device
List, create, and unlink customer accounts under a reseller partner
Run asynchronous bulk claim and unclaim jobs against device fleets
Inspect SIM lock state and metadata for partner-owned devices
Use Cases
Patterns agents use Android Device Provisioning Partner API for, with concrete tasks.
★ Reseller bulk device claiming
Resellers preparing a corporate Android shipment claim devices to a customer in zero-touch so the devices auto-enroll into the customer EMM on first boot. The async claim endpoint accepts large batches of IMEI or serial pairs and returns an operation handle the agent polls until completion. This eliminates manual EMM enrollment for fleets of hundreds or thousands of devices.
Submit a claimAsync request for 500 IMEI numbers under partner ID 1234 to customer ID 5678 and poll the returned operation until done.
Customer device inventory and configuration
Enterprise IT teams use the customer endpoints to list every device assigned to their organization, attach a zero-touch configuration that points at their EMM, and remove devices that have left the fleet. This keeps the company's view of corporate-owned hardware in sync with what was actually shipped by resellers.
List all devices for customer ID 5678, then apply configuration ID 99 to every device whose configuration is currently empty.
Pre-ship device verification
Before a reseller hands devices to the customer, an agent looks up each device by hardware identifier to confirm it is registered with the partner and not already claimed by another customer. This catches stocking errors and stops misrouted devices from blocking enrollment.
Call findByIdentifier with deviceIdentifier IMEI 123456789012345 under partnerId 1234 and report whether the device is unclaimed.
AI agent device fleet management
An AI agent acting as an MDM concierge accepts a reseller invoice, extracts IMEI numbers, and runs the claim, configure, and verify steps end-to-end through Jentic. The agent searches Jentic for the claim operation, loads the schema, and executes the call without the operator writing any HTTP code.
Read a CSV of 100 IMEI numbers, call the claim operation for each under customer 5678, and produce a summary of successes and failures.
Key Endpoints
24 endpoints — the android device provisioning partner api automates android zero-touch enrollment for device resellers, enterprise customers, and emm providers.
METHOD
PATH
DESCRIPTION
POST
/v1/partners/{+partnerId}/devices:claim
Claim a single device for a customer
POST
/v1/partners/{+partnerId}/devices:claimAsync
Claim a batch of devices asynchronously
POST
/v1/partners/{+partnerId}/devices:findByIdentifier
Find a device by IMEI, MEID, or serial
POST
/v1/partners/{+partnerId}/devices:findByOwner
Find devices by customer owner
GET
/v1/partners/{+partnerId}/customers
List customers under a partner
GET
/v1/customers
List customers visible to the caller
POST
/v1/partners/{+metadataOwnerId}/devices/{+deviceId}/metadata
Update device metadata
POST
/v1/partners/{+partnerId}/devices:claim
Claim a single device for a customer
POST
/v1/partners/{+partnerId}/devices:claimAsync
Claim a batch of devices asynchronously
POST
/v1/partners/{+partnerId}/devices:findByIdentifier
Find a device by IMEI, MEID, or serial
POST
/v1/partners/{+partnerId}/devices:findByOwner
Find devices by customer owner
GET
/v1/partners/{+partnerId}/customers
List customers under a partner
GET
/v1/customers
List customers visible to the caller
POST
/v1/partners/{+metadataOwnerId}/devices/{+deviceId}/metadata
Update device metadata
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.
A
Android Device Provisioning Partner API
- Foundational (D-)40/100
42
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability100
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
42
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D-Signals: 4
69%
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).
0%
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.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
73%
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.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
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 Android Device Provisioning Partner API by hand means configuring Google OAuth 2.0 for the zero-touch service account, minting short-lived scoped access tokens, and pointing calls at the androiddeviceprovisioning.googleapis.com host. Through Jentic you install once, import the Android Device Provisioning Partner API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the partner id in the URL path (/v1/partners/{+partnerId}/devices:claim, /customers), so a rule can pin your agent to one reseller partner: it can list customers and look up devices there and nothing else. You choose the operations it may call, so device claiming, claimAsync, or metadata writes are not included unless you add them.
Credential isolation
Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and exchanged for short-lived scoped access tokens at execution time. The client secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'claim an Android device' or 'find a device by IMEI', and Jentic returns the matching zero-touch 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 Android Device Provisioning Partner API through Jentic.
What authentication does the Android Device Provisioning Partner API use?
The API uses OAuth 2.0 with Google scopes. Through Jentic, the OAuth credentials are stored encrypted in your Jentic One instance and exchanged for scoped access tokens at call time so the raw client secret never enters the agent context.
Can I claim Android devices in bulk with this API?
Yes. The devices:claimAsync endpoint accepts a batch of device identifiers and returns a long-running operation handle. Poll the operation under /v1/operations until it completes to get per-device results.
What are the rate limits for the Android Device Provisioning Partner API?
Google enforces per-project quotas on the zero-touch API rather than fixed per-second limits, and asynchronous endpoints exist specifically so large batches do not hit synchronous quotas. Check the Google Cloud Console quota page for the live limit on your project.
How do I find a device by IMEI through Jentic?
Search Jentic for 'find android device by identifier', load the schema for partners.devices.findByIdentifier, and execute it with the partnerId and deviceIdentifier (IMEI, MEID, or serial). Jentic returns the matching device record if it is registered to your partner.
Is the Android Device Provisioning Partner API free?
Access is free but limited to approved zero-touch reseller and customer accounts. Your Google Cloud project must be enrolled as a partner and the API enabled before calls succeed.
What is the difference between claim and claimAsync?
The claim endpoint operates on a single device synchronously. The claimAsync endpoint accepts a batch and returns immediately with an operation, which you then poll. Use claimAsync for any batch larger than a handful of devices.
Can I limit what my agent is allowed to do with the Android Device Provisioning Partner API?
Yes. Because you self-host Jentic One, your own rules decide which zero-touch operations and credentials the agent may use. Since the partner id lives in the URL path (/v1/partners/{partnerId}/devices and /customers), you can pin the agent to a single reseller partner and grant only read operations like listing customers or finding a device by IMEI with findByIdentifier. Write operations such as devices:claim, devices:claimAsync, and device metadata updates stay off limits unless you explicitly add them.
GET STARTED