HumDay

Lists the DPCs (device policy controllers) in Google Android Device Provisioning Partner

A documented Google Android Device Provisioning Partner operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

Lists the DPCs (device policy controllers) that support zero-touch enrollment.

  • GETReads data · customersandroiddeviceprovisioning.googleapis.com/v1/{parent}/dpcs

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Android Device Provisioning Partner operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Google Android Device Provisioning Partner operations

All 23 Google Android Device Provisioning Partner operations

Questions

Can HumDay lists the dpcs (device policy controllers) in Google Android Device Provisioning Partner?
Yes. This operation is published in Google Android Device Provisioning Partner's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Does this change anything in my Google Android Device Provisioning Partner account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Android Device Provisioning Partner.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Android Device Provisioning Partner account.

Where this came from

Read from a published API description for Google Android Device Provisioning Partner at androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.