Skip to content
OpenParablePublic APIs

Android Device Provisioning Partner API API

by googleapis.com

No authHTTPSAnalytics
Open documentation ↗

Overview

Automates Android zero-touch enrollment for device resellers, customers, and EMMs.

Android Device Provisioning Partner API is an analytics API from googleapis.com. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 23 endpoints.

At a glance

Authentication
No auth
HTTPS
Yes
CORS
Unknown
Category
Analytics
Base URL
https://androiddeviceprovisioning.googleapis.com/
Version
v1
Endpoints
23
OpenAPI
Specification ↗
Spec updated
2023-04-21

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://androiddeviceprovisioning.googleapis.com/v1/customers" \
  -H "Accept: application/json"
JavaScript
const response = await fetch("https://androiddeviceprovisioning.googleapis.com/v1/customers", {
  method: "GET",
  headers: {
    "Accept": "application/json",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://androiddeviceprovisioning.googleapis.com/v1/customers",
    headers={
    "Accept": "application/json",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/v1/customersLists the user's customer accounts.
POST/v1/partners/{metadataOwnerId}/devices/{deviceId}/metadataUpdates reseller metadata associated with the device. Android devices only.
GET/v1/partners/{partnerId}/customersLists the customers that are enrolled to the reseller identified by the `partnerId` argument. This list includes customers that the reseller created and custome
POST/v1/partners/{partnerId}/devices:claimClaims a device for a customer and adds it to zero-touch enrollment. If the device is already claimed by another customer, the call returns an error.
POST/v1/partners/{partnerId}/devices:claimAsyncClaims a batch of devices for a customer asynchronously. Adds the devices to zero-touch enrollment. To learn more, read [Long‑running batch operations](/zero-to
POST/v1/partners/{partnerId}/devices:findByIdentifierFinds devices by hardware identifiers, such as IMEI.
POST/v1/partners/{partnerId}/devices:findByOwnerFinds devices claimed for customers. The results only contain devices registered to the reseller that's identified by the `partnerId` argument. The customer's d
POST/v1/partners/{partnerId}/devices:unclaimUnclaims a device from a customer and removes it from zero-touch enrollment.
POST/v1/partners/{partnerId}/devices:unclaimAsyncUnclaims a batch of devices for a customer asynchronously. Removes the devices from zero-touch enrollment. To learn more, read [Long‑running batch operations](/
POST/v1/partners/{partnerId}/devices:updateMetadataAsyncUpdates the reseller metadata attached to a batch of devices. This method updates devices asynchronously and returns an `Operation` that can be used to track pr
GET/v1/{name}Gets a device.
PATCH/v1/{name}Updates a configuration's field values.
DELETE/v1/{name}Deletes an unused configuration. The API call fails if the customer has devices with the configuration applied.
GET/v1/{parent}/configurationsLists a customer's configurations.
POST/v1/{parent}/configurationsCreates a new configuration. Once created, a customer can apply the configuration to devices.
GET/v1/{parent}/customersLists the customers of the vendor.
POST/v1/{parent}/customersCreates a customer for zero-touch enrollment. After the method returns successfully, admin and owner roles can manage devices and EMM configs by calling API met
GET/v1/{parent}/devicesLists a customer's devices.
POST/v1/{parent}/devices:applyConfigurationApplies a Configuration to the device to register the device for zero-touch enrollment. After applying a configuration to a device, the device automatically pro
POST/v1/{parent}/devices:removeConfigurationRemoves a configuration from device.
POST/v1/{parent}/devices:unclaimUnclaims a device from a customer and removes it from zero-touch enrollment. After removing a device, a customer must contact their reseller to register the dev
GET/v1/{parent}/dpcsLists the DPCs (device policy controllers) that support zero-touch enrollment.
GET/v1/{parent}/vendorsLists the vendors of the partner.

Questions

Does the Android Device Provisioning Partner API API need an API key?

No. The Android Device Provisioning Partner API API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.

Does the Android Device Provisioning Partner API API support HTTPS?

Yes, the Android Device Provisioning Partner API API is served over HTTPS.

How many endpoints does the Android Device Provisioning Partner API API have?

Its OpenAPI description lists 23 endpoints in version v1. All of them are shown on this page.

What are alternatives to the Android Device Provisioning Partner API API?

Other Analytics APIs include Google Play Integrity API, versionhistory.googleapis.com API, Doc Converter, Perspective Comment Analyzer API, Safe Browsing API.

Compare alternatives →

Google Play Integrity API

Analytics

The Play Integrity API helps you check that you're interacting with your genuine app on a genuine Android device powered by Google Play services. The Play Integrity API has replaced SafetyNet Attestation and Android Device Verification.

OAuth1 endpoints

versionhistory.googleapis.com API

Analytics

Version History API - Prod

No auth4 endpoints

Doc Converter

Analytics

This api converts file formats of OpenXml and OpenOffice documents formats to vector files (e.g., svg)

No auth1 endpoints

Perspective Comment Analyzer API

Analytics

The Perspective Comment Analyzer API provides information about the potential impact of a comment on a conversation (e.g. it can provide a score for the "toxicity" of a comment). Users can leverage the "SuggestCommentScore" method to submit corrections to improve Perspective over time. Users can set the "doNotStore" flag to ensure that all submitted comments are automatically deleted after scores are returned.

OAuth2 endpoints

Safe Browsing API

Analytics

Enables client applications to check web resources (most commonly URLs) against Google-generated lists of unsafe web resources. The Safe Browsing APIs are for non-commercial use only. If you need to use APIs to detect malicious URLs for commercial purposes – meaning “for sale or revenue-generating purposes” – please refer to the Web Risk API.

No auth7 endpoints

Web Fonts Developer API

Analytics

The Google Web Fonts Developer API lets you retrieve information about web fonts served by Google.

No auth1 endpoints

Listed from APIs.guru (CC0).