Android Device Provisioning Partner API

Name: Android Device Provisioning Partner API API
Brand: Android Device Provisioning Partner API
Availability: InStock

✓ Official Vendor SpecIdentity 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.

Quickstart

Get started with Android Device Provisioning Partner API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"claim an android device for zero touch enrollment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Android Device Provisioning Partner API 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

GET STARTED

Start building with Android Device Provisioning Partner API API

Explore with Jentic

View OpenAPI Spec

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.

Use Cases

Patterns agents use Android Device Provisioning Partner API 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

Why though Jentic?

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

Credential isolation

Google OAuth client credentials and refresh tokens for the zero-touch service account are stored encrypted in the Jentic vault. Agents receive a short-lived scoped access token at execution time and never see the raw client secret.

Intent-based discovery

Agents search Jentic with phrases like 'claim an android device' or 'find device by imei' and Jentic returns the matching zero-touch operation along with its input schema, so the agent calls the right endpoint without browsing the partner portal docs.

Time to first call

Direct integration: 2-4 days for OAuth setup, partner approval workflow, and async polling logic. Through Jentic: under one hour to search, load, and execute claim operations.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Android Management API

Manages Android devices and apps after they are enrolled in zero-touch.

Use Android Management for ongoing policy, app, and command control once devices have been claimed and shipped via Device Provisioning.

Complementary

Google Play EMM API

Deploys managed Google Play apps to enrolled Android Enterprise devices.

Use the EMM API to push apps and manage entitlements after Device Provisioning has registered the device.

Complementary

API Keys API

Manages API keys for Google Cloud projects that call zero-touch.

Use API Keys to provision and rotate the credentials your zero-touch reseller integration depends on.

FAQs

Specific to using Android Device Provisioning Partner API 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 the Jentic vault 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.