syncing market data_
Automates Android zero-touch enrollment for device resellers, customers, and EMMs.
Automates Android zero-touch enrollment for device resellers, customers, and EMMs. --- Public API proxied through Ozma. **Claim this listing** to monetize and manage pricing.
No score data yet
| Method | Path | Summary | Price |
|---|---|---|---|
| GET | /v1/customers | Lists the user's customer accounts. | 1c |
| POST | /v1/partners/{metadataOwnerId}/devices/{deviceId}/metadata | Updates reseller metadata associated with the device. Android devices only. | 1c |
| GET | /v1/partners/{partnerId}/customers | Lists the customers that are enrolled to the reseller identified by the `partnerId` argument. This list includes customers that the reseller created and customers that enrolled themselves using the portal. | 1c |
| POST | /v1/partners/{partnerId}/devices:claim | Claims 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. | 1c |
| POST | /v1/partners/{partnerId}/devices:claimAsync | Claims a batch of devices for a customer asynchronously. Adds the devices to zero-touch enrollment. To learn more, read [Long‑running batch operations](/zero-touch/guides/how-it-works#operations). | 1c |
| POST | /v1/partners/{partnerId}/devices:findByIdentifier | Finds devices by hardware identifiers, such as IMEI. | 1c |
| POST | /v1/partners/{partnerId}/devices:findByOwner | Finds devices claimed for customers. The results only contain devices registered to the reseller that's identified by the `partnerId` argument. The customer's devices purchased from other resellers don't appear in the results. | 1c |
| POST | /v1/partners/{partnerId}/devices:unclaim | Unclaims a device from a customer and removes it from zero-touch enrollment. | 1c |
| POST | /v1/partners/{partnerId}/devices:unclaimAsync | Unclaims a batch of devices for a customer asynchronously. Removes the devices from zero-touch enrollment. To learn more, read [Long‑running batch operations](/zero-touch/guides/how-it-works#operations). | 1c |
| POST | /v1/partners/{partnerId}/devices:updateMetadataAsync | Updates the reseller metadata attached to a batch of devices. This method updates devices asynchronously and returns an `Operation` that can be used to track progress. Read [Long‑running batch operations](/zero-touch/guides/how-it-works#operations). Android Devices only. | 1c |
| DELETE | /v1/{name} | Deletes an unused configuration. The API call fails if the customer has devices with the configuration applied. | 1c |
| GET | /v1/{name} | Gets a device. | 1c |
| PATCH | /v1/{name} | Updates a configuration's field values. | 1c |
| GET | /v1/{parent}/configurations | Lists a customer's configurations. | 1c |
| POST | /v1/{parent}/configurations | Creates a new configuration. Once created, a customer can apply the configuration to devices. | 1c |
| GET | /v1/{parent}/customers | Lists the customers of the vendor. | 1c |
| POST | /v1/{parent}/customers | Creates a customer for zero-touch enrollment. After the method returns successfully, admin and owner roles can manage devices and EMM configs by calling API methods or using their zero-touch enrollment portal. The customer receives an email that welcomes them to zero-touch enrollment and explains how to sign into the portal. | 1c |
| GET | /v1/{parent}/devices | Lists a customer's devices. | 1c |
| POST | /v1/{parent}/devices:applyConfiguration | Applies a Configuration to the device to register the device for zero-touch enrollment. After applying a configuration to a device, the device automatically provisions itself on first boot, or next factory reset. | 1c |
| POST | /v1/{parent}/devices:removeConfiguration | Removes a configuration from device. | 1c |
| POST | /v1/{parent}/devices:unclaim | Unclaims 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 device into zero-touch enrollment again. | 1c |
| GET | /v1/{parent}/dpcs | Lists the DPCs (device policy controllers) that support zero-touch enrollment. | 1c |
| GET | /v1/{parent}/vendors | Lists the vendors of the partner. | 1c |
ozma register && ozma call android-device-provisioning-partner-api /v1/customers --jsoncurl -H "Authorization: Bearer $OZMA_KEY" \
https://gateway.ozma.app/v1/proxy/android-device-provisioning-partner-api/v1/customers# Python
client.proxy_call("android-device-provisioning-partner-api", "/v1/customers")Own this API? Claim the listing to manage pricing and receive payouts.