Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

DescriptionGet the details of operations carried out on a selected device.
Resource Path/{type}/{id}
URL/mdm-admin/operations/{type}/{id}
HTTP MethodGET
Request/Response Formatapplication/json
cURL command
curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/operation/{type}/{id}
  • For more information on how to generate the <EMM_API_TOKEN>, see Generating the EMM API Token.
  • By default, <EMM_HOST> is localhost. However, if you are using a public IP, the respective IP address or domain needs to be specified.
  • By default, <EMM_HTTPS_PORT> has been set to 9443. However, if the port offset has been incremented by n, the default port value needs to be incremented by n.
  • Define the device type as the value for {type}. Example: ios, android or windows.
  • Define the device ID as the value for {id}.

Example:

curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer 33392fb365b3ac693b405b565ddc8a3a" -k -v https://localhost:9443/mdm-admin/operations/ios/f409r4c55924rt4af9a44tts15y9d6cd56h1047d
 Sample output
> GET /mdm-admin/operations/ios/f409r4c55924rt4af9a44tts15y9d6cd56h1047d HTTP/1.1
> Host: localhost:9443
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Type: application/json
> Authorization: Bearer 686f9b27a6f2d23df5ba94322b9847e1
< HTTP/1.1 200 OK
< Cache-Control: private
< Expires: Thu, 01 Jan 1970 05:30:00 IST
< Date: Thu, 18 Feb 2016 10:57:07 GMT
< Content-Type: application/json
< Content-Length: 1526
< Server: WSO2 Carbon Server
[{"code":"DEVICE_INFO","type":"COMMAND","id":25,"status":"PENDING","receivedTimeStamp":"","createdTimeStamp":"2016-02-18 15:31:05.455","isEnabled":false},{"code":"APPLICATION_LIST","type":"COMMAND","id":24,"status":"PENDING","receivedTimeStamp":"","createdTimeStamp":"2016-02-18 15:31:02.951","isEnabled":false},{"code":"ALARM","type":"COMMAND","id":23,"status":"PENDING","receivedTimeStamp":"","createdTimeStamp":"2016-02-18 14:57:42.784","isEnabled":false}]
Sample JSON Output
Definition 
{  
      "code":"ALARM",
      "type":"COMMAND",
      "id":22,
      "status":"COMPLETED",
      "receivedTimeStamp":"2016-02-18 14:57:09.976",
      "createdTimeStamp":"2016-02-18 14:57:08.976",
      "isEnabled":false
   } 

Property Value

Description

code

The code of the operation that you carried out. For example the code of the operation carried out to ring the alarm is ALARM.

type

The operation type that was carried out on the device. The operations types can be one of the following:

  • COMMAND
  • PROFILE
idThe operations carried out on a device is recorded in a database table. The ID of the operation in the database table is given as the ID in the output.
status

The status of the operation that has been carried out on a device. The operation status can be any one of the following:

  • IN-PROGRESS - The operation is processing on the EMM server side and has not yet been delivered to the device.
  • PENDING - The operation is delivered to the device but the response from the device is pending.
  • COMPLETED - The operation is delivered to the device and the server has received a response back from the device.
  • ERROR - An error has occurred while carrying out the operation.
receivedTimeStampThe time WSO2 EMM received the response from the device.
createdTimeStampThe time when the operation was requested to be carried out.
isEnabledIf the assigned value is true it indicates that a policy is enforced on the device. If the assigned value is false it indicates that a policy is not enforced on a device.
  • No labels