Api-roll 33: 2016-03-14

discovery/googleapis/androidenterprise__v1.json

Index: discovery/googleapis/androidenterprise__v1.json
diff --git a/discovery/googleapis/androidenterprise__v1.json b/discovery/googleapis/androidenterprise__v1.json
index 29d0a39189eca2f8d0ed9cb7eff7379252ca7d85..a56837f71d5348f492938a35624c745be5d03b1e 100644
--- a/discovery/googleapis/androidenterprise__v1.json
+++ b/discovery/googleapis/androidenterprise__v1.json
@@ -15,7 +15,7 @@
     "description": "Allows MDMs/EMMs and enterprises to manage the deployment of apps to Android for Work users.",
     "discoveryVersion": "v1",
     "documentationLink": "https://developers.google.com/android/work/play/emm-api",
-    "etag": "\"bRFOOrZKfO9LweMbPqu0kcu6De8/4xdfCsFKqY63nj0AgziCWDL1CtA\"",
+    "etag": "\"bRFOOrZKfO9LweMbPqu0kcu6De8/oDGCBWQ3TbSodDSQVvns_CkjrJY\"",
     "icons": {
         "x16": "https://www.google.com/images/icons/product/android-16.png",
         "x32": "https://www.google.com/images/icons/product/android-32.png"
@@ -584,7 +584,7 @@
         "enterprises": {
             "methods": {
                 "delete": {
-                    "description": "Deletes the binding between the MDM and enterprise. This is now deprecated; use this to unenroll customers that were previously enrolled with the 'insert' call, then enroll them again with the 'enroll' call.",
+                    "description": "Deletes the binding between the EMM and enterprise. This is now deprecated; use this to unenroll customers that were previously enrolled with the 'insert' call, then enroll them again with the 'enroll' call.",
                     "httpMethod": "DELETE",
                     "id": "androidenterprise.enterprises.delete",
                     "parameterOrder": [
@@ -604,7 +604,7 @@
                     ]
                 },
                 "enroll": {
-                    "description": "Enrolls an enterprise with the calling MDM.",
+                    "description": "Enrolls an enterprise with the calling EMM.",
                     "httpMethod": "POST",
                     "id": "androidenterprise.enterprises.enroll",
                     "parameterOrder": [
@@ -612,7 +612,7 @@
                     ],
                     "parameters": {
                         "token": {
-                            "description": "The token provided by the enterprise to register the MDM.",
+                            "description": "The token provided by the enterprise to register the EMM.",
                             "location": "query",
                             "required": true,
                             "type": "string"
@@ -676,7 +676,7 @@
                     ]
                 },
                 "insert": {
-                    "description": "Establishes the binding between the MDM and an enterprise. This is now deprecated; use enroll instead.",
+                    "description": "Establishes the binding between the EMM and an enterprise. This is now deprecated; use enroll instead.",
                     "httpMethod": "POST",
                     "id": "androidenterprise.enterprises.insert",
                     "parameterOrder": [
@@ -684,7 +684,7 @@
                     ],
                     "parameters": {
                         "token": {
-                            "description": "The token provided by the enterprise to register the MDM.",
+                            "description": "The token provided by the enterprise to register the EMM.",
                             "location": "query",
                             "required": true,
                             "type": "string"
@@ -725,7 +725,7 @@
                     ]
                 },
                 "sendTestPushNotification": {
-                    "description": "Sends a test push notification to validate the MDM integration with the Google Cloud Pub/Sub service for this enterprise.",
+                    "description": "Sends a test push notification to validate the EMM integration with the Google Cloud Pub/Sub service for this enterprise.",
                     "httpMethod": "POST",
                     "id": "androidenterprise.enterprises.sendTestPushNotification",
                     "parameterOrder": [
@@ -800,7 +800,7 @@
                     ]
                 },
                 "unenroll": {
-                    "description": "Unenrolls an enterprise from the calling MDM.",
+                    "description": "Unenrolls an enterprise from the calling EMM.",
                     "httpMethod": "POST",
                     "id": "androidenterprise.enterprises.unenroll",
                     "parameterOrder": [
@@ -1527,7 +1527,7 @@
                     ]
                 },
                 "updatePermissions": {
-                    "description": "Updates the set of Android app permissions for this app that have been accepted by the enterprise.",
+                    "description": "This method has been deprecated. To programmatically approve applications, you must use the iframe mechanism via the  generateApprovalUrl and  approve methods of the Products resource. For more information, see the  Play EMM API usage requirements.\n\nThe updatePermissions method (deprecated) updates the set of Android app permissions for this app that have been accepted by the enterprise.",
                     "httpMethod": "PUT",
                     "id": "androidenterprise.products.updatePermissions",
                     "parameterOrder": [
@@ -1958,7 +1958,7 @@
         "users": {
             "methods": {
                 "generateToken": {
-                    "description": "Generates a token (activation code) to allow this user to configure their work account in the Android Setup Wizard. Revokes any previously generated token.",
+                    "description": "Generates a token (activation code) to allow this user to configure their work account in the Android Setup Wizard. Revokes any previously generated token.\n\nThis call only works with Google managed accounts.",
                     "httpMethod": "POST",
                     "id": "androidenterprise.users.generateToken",
                     "parameterOrder": [
@@ -2048,7 +2048,7 @@
                     ]
                 },
                 "list": {
-                    "description": "Looks up a user by email address. This only works for Google managed users.",
+                    "description": "Looks up a user by their primary email address.",
                     "httpMethod": "GET",
                     "id": "androidenterprise.users.list",
                     "parameterOrder": [
@@ -2140,7 +2140,7 @@
             }
         }
     },
-    "revision": "20160106",
+    "revision": "20160302",
     "rootUrl": "https://www.googleapis.com/",
     "schemas": {
         "AppRestrictionsSchema": {
@@ -2348,7 +2348,7 @@
             "type": "object"
         },
         "Device": {
-            "description": "A device resource represents a mobile device managed by the MDM and belonging to a specific enterprise user.\n\nThis collection cannot be modified via the API; it is automatically populated as devices are set up to be managed.",
+            "description": "A device resource represents a mobile device managed by the EMM and belonging to a specific enterprise user.\n\nThis collection cannot be modified via the API; it is automatically populated as devices are set up to be managed.",
             "id": "Device",
             "properties": {
                 "androidId": {
@@ -2361,7 +2361,7 @@
                     "type": "string"
                 },
                 "managementType": {
-                    "description": "The mechanism by which this device is managed by the MDM. \"managedDevice\" means that the MDM's app is a device owner. \"managedProfile\" means that the MDM's app is the profile owner (and there is a separate personal profile which is not managed). \"containerApp\" means that the MDM's app is managing the Android for Work container app on the device.",
+                    "description": "The mechanism by which this device is managed by the EMM. \"managedDevice\" means that the EMM's app is a device owner. \"managedProfile\" means that the EMM's app is the profile owner (and there is a separate personal profile which is not managed). \"containerApp\" means that the EMM's app is managing the Android for Work container app on the device.",
                     "type": "string"
                 }
             },
@@ -2403,7 +2403,7 @@
             "type": "object"
         },
         "Enterprise": {
-            "description": "An enterprise resource represents a binding between an organisation and their MDM.\n\nTo create an enterprise, an admin of the enterprise must first go through a Play for Work sign-up flow. At the end of this the admin will be presented with a token (a short opaque alphanumeric string). They must then present this to the MDM, who then supplies it to the enroll method. Until this is done the MDM will not have any access to the enterprise.\n\nAfter calling enroll the MDM should call setAccount to specify the service account that will be allowed to act on behalf of the enterprise, which will be required for access to the enterprise's data through this API. Only one call of setAccount is allowed for a given enterprise; the only way to change the account later is to unenroll the enterprise and enroll it again (obtaining a new token).\n\nThe MDM can unenroll an enterprise in order to sever the binding between them. Re-enrolling an enterprise is possible, but requires a new token to be retrieved. Enterprises.unenroll requires the MDM's credentials (as enroll does), not the enterprise's. Enterprises.unenroll can only be used for enterprises that were previously enrolled with the enroll call. Any enterprises that were enrolled using the (deprecated) Enterprises.insert call must be unenrolled with Enterprises.delete and can then be re-enrolled using the Enterprises.enroll call.\n\nThe ID for an enterprise is an opaque string. It is returned by insert and enroll and can also be retrieved if the enterprise's primary domain is known using the list method.",
+            "description": "An enterprise resource represents a binding between an organisation and their EMM.\n\nTo create an enterprise, an admin of the enterprise must first go through a Play for Work sign-up flow. At the end of this the admin will be presented with a token (a short opaque alphanumeric string). They must then present this to the EMM, who then supplies it to the enroll method. Until this is done the EMM will not have any access to the enterprise.\n\nAfter calling enroll the EMM should call setAccount to specify the service account that will be allowed to act on behalf of the enterprise, which will be required for access to the enterprise's data through this API. Only one call of setAccount is allowed for a given enterprise; the only way to change the account later is to unenroll the enterprise and enroll it again (obtaining a new token).\n\nThe EMM can unenroll an enterprise in order to sever the binding between them. Re-enrolling an enterprise is possible, but requires a new token to be retrieved. Enterprises.unenroll requires the EMM's credentials (as enroll does), not the enterprise's. Enterprises.unenroll can only be used for enterprises that were previously enrolled with the enroll call. Any enterprises that were enrolled using the (deprecated) Enterprises.insert call must be unenrolled with Enterprises.delete and can then be re-enrolled using the Enterprises.enroll call.\n\nThe ID for an enterprise is an opaque string. It is returned by insert and enroll and can also be retrieved if the enterprise's primary domain is known using the list method.",
             "id": "Enterprise",
             "properties": {
                 "id": {
@@ -2481,7 +2481,7 @@
             "type": "object"
         },
         "Entitlement": {
-            "description": "The existence of an entitlement resource means that a user has the right to use a particular app on any of their devices. This might be because the app is free or because they have been allocated a license to the app from a group license purchased by the enterprise.\n\nIt should always be true that a user has an app installed on one of their devices only if they have an entitlement to it. So if an entitlement is deleted, the app will be uninstalled from all devices. Similarly if the user installs an app (and is permitted to do so), or the MDM triggers an install of the app, an entitlement to that app is automatically created. If this is impossible - e.g. the enterprise has not purchased sufficient licenses - then installation fails.\n\nNote that entitlements are always user specific, not device specific; a user may have an entitlement even though they have not installed the app anywhere. Once they have an entitlement they can install the app on multiple devices.\n\nThe API can be used to create an entitlement. If the app is a free app, a group license for that app is created. If it's a paid app, creating the entitlement consumes one license; it remains consumed until the entitlement is removed. Optionally an installation of the app on all the user's managed devices can be triggered at the time the entitlement is created. An entitlement cannot be created for an app if the app requires permissions that the enterprise has not yet accepted.\n\nEntitlements for paid apps that are due to purchases by the user on a non-managed profile will have \"userPurchase\" as entitlement reason; those entitlements cannot be removed via the API.",
+            "description": "The existence of an entitlement resource means that a user has the right to use a particular app on any of their devices. This might be because the app is free or because they have been allocated a license to the app from a group license purchased by the enterprise.\n\nIt should always be true that a user has an app installed on one of their devices only if they have an entitlement to it. So if an entitlement is deleted, the app will be uninstalled from all devices. Similarly if the user installs an app (and is permitted to do so), or the EMM triggers an install of the app, an entitlement to that app is automatically created. If this is impossible - e.g. the enterprise has not purchased sufficient licenses - then installation fails.\n\nNote that entitlements are always user specific, not device specific; a user may have an entitlement even though they have not installed the app anywhere. Once they have an entitlement they can install the app on multiple devices.\n\nThe API can be used to create an entitlement. If the app is a free app, a group license for that app is created. If it's a paid app, creating the entitlement consumes one license; it remains consumed until the entitlement is removed. Optionally an installation of the app on all the user's managed devices can be triggered at the time the entitlement is created. An entitlement cannot be created for an app if the app requires permissions that the enterprise has not yet accepted.\n\nEntitlements for paid apps that are due to purchases by the user on a non-managed profile will have \"userPurchase\" as entitlement reason; those entitlements cannot be removed via the API.",
             "id": "Entitlement",
             "properties": {
                 "kind": {
@@ -2651,7 +2651,7 @@
             "type": "object"
         },
         "Permission": {
-            "description": "A permission represents some extra capability, to be granted to an Android app, which requires explicit consent. An enterprise admin must consent to these permissions on behalf of their users before an entitlement for the app can be created.\n\nThe permissions collection is read-only. The information provided for each permission (localized name and description) is intended to be used in the MDM user interface when obtaining consent from the enterprise.",
+            "description": "A permission represents some extra capability, to be granted to an Android app, which requires explicit consent. An enterprise admin must consent to these permissions on behalf of their users before an entitlement for the app can be created.\n\nThe permissions collection is read-only. The information provided for each permission (localized name and description) is intended to be used in the EMM user interface when obtaining consent from the enterprise.",
             "id": "Permission",
             "properties": {
                 "description": {
@@ -2675,7 +2675,7 @@
             "type": "object"
         },
         "Product": {
-            "description": "A product represents an app in the Google Play Store that is available to at least some users in the enterprise. (Some apps are restricted to a single enterprise, and no information about them is made available outside that enterprise.)\n\nThe information provided for each product (localized name, icon, link to the full Google Play details page) is intended to allow a basic representation of the product within an MDM user interface.",
+            "description": "A product represents an app in the Google Play Store that is available to at least some users in the enterprise. (Some apps are restricted to a single enterprise, and no information about them is made available outside that enterprise.)\n\nThe information provided for each product (localized name, icon, link to the full Google Play details page) is intended to allow a basic representation of the product within an EMM user interface.",
             "id": "Product",
             "properties": {
                 "appVersion": {
@@ -2930,7 +2930,7 @@
             "type": "object"
         },
         "User": {
-            "description": "A user resource represents an individual user within the enterprise's domain.\n\nNote that each user is associated with a Google account based on the user's corporate email address (which must be in one of the enterprise's domains). As part of installing an MDM app to manage a device the Google account must be provisioned to the device, and so the user resource must be created before that. This can be done using the Google Admin SDK Directory API.\n\nThe ID for a user is an opaque string. It can be retrieved using the list method queried by the user's primary email address.",
+            "description": "A user resource represents an individual user within the enterprise's domain.\n\nNote that each user is associated with a Google account based on the user's corporate email address (which must be in one of the enterprise's domains). As part of installing the EMM's DPC app to manage a device the Google account must be provisioned to the device, and so the user resource must be created before that. This can be done using the Google Admin SDK Directory API.\n\nThe ID for a user is an opaque string. It can be retrieved using the list method queried by the user's primary email address.",
             "id": "User",
             "properties": {
                 "id": {
@@ -2950,7 +2950,7 @@
             "type": "object"
         },
         "UserToken": {
-            "description": "A UserToken is used by a user when setting up a managed device or profile with their work account on a device. When the user enters their email address and token (activation code) the appropriate MDM app can be automatically downloaded.",
+            "description": "A UserToken is used by a user when setting up a managed device or profile with their work account on a device. When the user enters their email address and token (activation code) the appropriate EMM app can be automatically downloaded.",
             "id": "UserToken",
             "properties": {
                 "kind": {