1<html><body>
2<style>
3
4body, h1, h2, h3, div, span, p, pre, a {
5  margin: 0;
6  padding: 0;
7  border: 0;
8  font-weight: inherit;
9  font-style: inherit;
10  font-size: 100%;
11  font-family: inherit;
12  vertical-align: baseline;
13}
14
15body {
16  font-size: 13px;
17  padding: 1em;
18}
19
20h1 {
21  font-size: 26px;
22  margin-bottom: 1em;
23}
24
25h2 {
26  font-size: 24px;
27  margin-bottom: 1em;
28}
29
30h3 {
31  font-size: 20px;
32  margin-bottom: 1em;
33  margin-top: 1em;
34}
35
36pre, code {
37  line-height: 1.5;
38  font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39}
40
41pre {
42  margin-top: 0.5em;
43}
44
45h1, h2, h3, p {
46  font-family: Arial, sans serif;
47}
48
49h1, h2, h3 {
50  border-bottom: solid #CCC 1px;
51}
52
53.toc_element {
54  margin-top: 0.5em;
55}
56
57.firstline {
58  margin-left: 2 em;
59}
60
61.method  {
62  margin-top: 1em;
63  border: solid 1px #CCC;
64  padding: 1em;
65  background: #EEE;
66}
67
68.details {
69  font-weight: bold;
70  font-size: 14px;
71}
72
73</style>
74
75<h1><a href="androiddeviceprovisioning_v1.html">Android Device Provisioning Partner API</a> . <a href="androiddeviceprovisioning_v1.customers.html">customers</a> . <a href="androiddeviceprovisioning_v1.customers.configurations.html">configurations</a></h1>
76<h2>Instance Methods</h2>
77<p class="toc_element">
78  <code><a href="#close">close()</a></code></p>
79<p class="firstline">Close httplib2 connections.</p>
80<p class="toc_element">
81  <code><a href="#create">create(parent, body=None, x__xgafv=None)</a></code></p>
82<p class="firstline">Creates a new configuration. Once created, a customer can apply the configuration to devices.</p>
83<p class="toc_element">
84  <code><a href="#delete">delete(name, x__xgafv=None)</a></code></p>
85<p class="firstline">Deletes an unused configuration. The API call fails if the customer has devices with the configuration applied.</p>
86<p class="toc_element">
87  <code><a href="#get">get(name, x__xgafv=None)</a></code></p>
88<p class="firstline">Gets the details of a configuration.</p>
89<p class="toc_element">
90  <code><a href="#list">list(parent, x__xgafv=None)</a></code></p>
91<p class="firstline">Lists a customer's configurations.</p>
92<p class="toc_element">
93  <code><a href="#patch">patch(name, body=None, updateMask=None, x__xgafv=None)</a></code></p>
94<p class="firstline">Updates a configuration's field values.</p>
95<h3>Method Details</h3>
96<div class="method">
97    <code class="details" id="close">close()</code>
98  <pre>Close httplib2 connections.</pre>
99</div>
100
101<div class="method">
102    <code class="details" id="create">create(parent, body=None, x__xgafv=None)</code>
103  <pre>Creates a new configuration. Once created, a customer can apply the configuration to devices.
104
105Args:
106  parent: string, Required. The customer that manages the configuration. An API resource name in the format `customers/[CUSTOMER_ID]`. (required)
107  body: object, The request body.
108    The object takes the form of:
109
110{ # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
111  &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
112  &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
113  &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
114  &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
115  &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
116  &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
117  &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
118  &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
119  &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
120  &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
121}
122
123  x__xgafv: string, V1 error format.
124    Allowed values
125      1 - v1 error format
126      2 - v2 error format
127
128Returns:
129  An object of the form:
130
131    { # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
132  &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
133  &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
134  &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
135  &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
136  &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
137  &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
138  &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
139  &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
140  &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
141  &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
142}</pre>
143</div>
144
145<div class="method">
146    <code class="details" id="delete">delete(name, x__xgafv=None)</code>
147  <pre>Deletes an unused configuration. The API call fails if the customer has devices with the configuration applied.
148
149Args:
150  name: string, Required. The configuration to delete. An API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. If the configuration is applied to any devices, the API call fails. (required)
151  x__xgafv: string, V1 error format.
152    Allowed values
153      1 - v1 error format
154      2 - v2 error format
155
156Returns:
157  An object of the form:
158
159    { # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
160}</pre>
161</div>
162
163<div class="method">
164    <code class="details" id="get">get(name, x__xgafv=None)</code>
165  <pre>Gets the details of a configuration.
166
167Args:
168  name: string, Required. The configuration to get. An API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. (required)
169  x__xgafv: string, V1 error format.
170    Allowed values
171      1 - v1 error format
172      2 - v2 error format
173
174Returns:
175  An object of the form:
176
177    { # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
178  &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
179  &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
180  &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
181  &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
182  &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
183  &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
184  &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
185  &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
186  &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
187  &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
188}</pre>
189</div>
190
191<div class="method">
192    <code class="details" id="list">list(parent, x__xgafv=None)</code>
193  <pre>Lists a customer&#x27;s configurations.
194
195Args:
196  parent: string, Required. The customer that manages the listed configurations. An API resource name in the format `customers/[CUSTOMER_ID]`. (required)
197  x__xgafv: string, V1 error format.
198    Allowed values
199      1 - v1 error format
200      2 - v2 error format
201
202Returns:
203  An object of the form:
204
205    { # Response message of customer&#x27;s listing configuration.
206  &quot;configurations&quot;: [ # The configurations.
207    { # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
208      &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
209      &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
210      &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
211      &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
212      &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
213      &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
214      &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
215      &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
216      &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
217      &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
218    },
219  ],
220}</pre>
221</div>
222
223<div class="method">
224    <code class="details" id="patch">patch(name, body=None, updateMask=None, x__xgafv=None)</code>
225  <pre>Updates a configuration&#x27;s field values.
226
227Args:
228  name: string, Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server. (required)
229  body: object, The request body.
230    The object takes the form of:
231
232{ # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
233  &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
234  &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
235  &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
236  &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
237  &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
238  &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
239  &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
240  &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
241  &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
242  &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
243}
244
245  updateMask: string, Required. The field mask applied to the target `Configuration` before updating the fields. To learn more about using field masks, read [FieldMask](/protocol-buffers/docs/reference/google.protobuf#fieldmask) in the Protocol Buffers documentation.
246  x__xgafv: string, V1 error format.
247    Allowed values
248      1 - v1 error format
249      2 - v2 error format
250
251Returns:
252  An object of the form:
253
254    { # A configuration collects the provisioning options for Android devices. Each configuration combines the following: * The EMM device policy controller (DPC) installed on the devices. * EMM policies enforced on the devices. * Metadata displayed on the device to help users during setup. Customers can add as many configurations as they need. However, zero-touch enrollment works best when a customer sets a default configuration that&#x27;s applied to any new devices the organization purchases.
255  &quot;companyName&quot;: &quot;A String&quot;, # Required. The name of the organization. Zero-touch enrollment shows this organization name to device users during device provisioning.
256  &quot;configurationId&quot;: &quot;A String&quot;, # Output only. The ID of the configuration. Assigned by the server.
257  &quot;configurationName&quot;: &quot;A String&quot;, # Required. A short name that describes the configuration&#x27;s purpose. For example, _Sales team_ or _Temporary employees_. The zero-touch enrollment portal displays this name to IT admins.
258  &quot;contactEmail&quot;: &quot;A String&quot;, # Required. The email address that device users can contact to get help. Zero-touch enrollment shows this email address to device users before device provisioning. The value is validated on input.
259  &quot;contactPhone&quot;: &quot;A String&quot;, # Required. The telephone number that device users can call, using another device, to get help. Zero-touch enrollment shows this number to device users before device provisioning. Accepts numerals, spaces, the plus sign, hyphens, and parentheses.
260  &quot;customMessage&quot;: &quot;A String&quot;, # A message, containing one or two sentences, to help device users get help or give them more details about what’s happening to their device. Zero-touch enrollment shows this message before the device is provisioned.
261  &quot;dpcExtras&quot;: &quot;A String&quot;, # The JSON-formatted EMM provisioning extras that are passed to the DPC.
262  &quot;dpcResourcePath&quot;: &quot;A String&quot;, # Required. The resource name of the selected DPC (device policy controller) in the format `customers/[CUSTOMER_ID]/dpcs/*`. To list the supported DPCs, call `customers.dpcs.list`.
263  &quot;isDefault&quot;: True or False, # Required. Whether this is the default configuration that zero-touch enrollment applies to any new devices the organization purchases in the future. Only one customer configuration can be the default. Setting this value to `true`, changes the previous default configuration&#x27;s `isDefault` value to `false`.
264  &quot;name&quot;: &quot;A String&quot;, # Output only. The API resource name in the format `customers/[CUSTOMER_ID]/configurations/[CONFIGURATION_ID]`. Assigned by the server.
265}</pre>
266</div>
267
268</body></html>