Description | Using this REST API you are able to request for Android device details. Once this REST API is executed it will be in the Android operation queue until the device calls the server to retrieve the list of operations that needs to be executed on the device. For more information on the REST API command used by the device to get the pending operations queued up on the server end, see Getting Pending Android Device Operations . | ||||||
---|---|---|---|---|---|---|---|
Resource Path | /device-info | ||||||
URL | /mdm-android-agent/operation/device-info | ||||||
HTTP Method | POST | ||||||
Request/Response Format | application/json | ||||||
cURL command | curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -d @'<JSON_PAYLOAD>' -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-android-agent/operation/device-info
Example: curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer e56974e8bf5df15748f89c6c5da9835d" -d @'operation.json' -k -v https://localhost:9443/mdm-android-agent/operation/device-info Once this operation is invoked via the REST API, the user needs to refresh the device management page in the EMM console to see the latest device information. For more information, see Viewing Device Specific Information. | ||||||
Sample output | > POST /mdm-android-agent/operation/device-info HTTP/1.1 > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8| zlib/1.2.5 > Host: localhost:9443 > Accept: */* > Content-Type: application/json > Authorization: Bearer e56974e8bf5df15748f89c6c5da9835d > Content-Length: 21 < HTTP/1.1 201 Created < Date: Wed, 10 Jun 2015 09:42:18 GMT < Content-Length: 0 < Server: WSO2 Carbon Server | ||||||
Sample JSON Definition | [ "d8:50:e6:2f:6a:8b", "a5:60:e6:2g:6a:5b" ]
|
Unknown macro: {next_previous_link3}
Manage space
Manage content
Integrations