The data forwarding and server-side subscription features of IoT Platform process and forward data based on the data formats of topics. Topics can be grouped into custom topics, basic communication topics, and Thing Specification Language (TSL)-based topics. This article describes the data formats of basic communication topics and TSL-based communication topics.

Submit device status

Topic: /as/mqtt/status/${productKey}/${deviceName}

You can use this topic to retrieve the online or offline status of devices.

Format of online status data:

{
    "status":"online",
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"al12345****",
    "deviceName":"deviceName1234",
    "time":"2018-08-31 15:32:28.205",
    "utcTime":"2018-08-31T07:32:28.205Z",
    "lastTime":"2018-08-31 15:32:28.195",
    "utcLastTime":"2018-08-31T07:32:28.195Z",
    "clientIp":"192.0.2.1"
}

Format of offline status data:

{
    "status":"offline",
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "offlineReasonCode":427,
    "productKey":"al12345****",
    "deviceName":"deviceName1234",
    "time":"2018-08-31 15:32:28.205",
    "utcTime":"2018-08-31T07:32:28.205Z",
    "lastTime":"2018-08-31 15:32:28.195",
    "utcLastTime":"2018-08-31T07:32:28.195Z",
    "clientIp":"192.0.2.1"
}

The following table describes the parameters.

Parameter Type Description
status String The device status. Valid values:
  • online: The device is online.
  • offline: The device is offline.
iotId String The ID of the device in IoT Platform.
offlineReasonCode Integer The error code returned if the device goes offline. For more information, see Device behavior-related error codes.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
time String The time when the status notification was sent.
utcTime String The time in UTC when the status notification was sent.
lastTime String The time when the last communication occurred before the status changed.

The time when a message is received from a device is not the same as the time when the device status changes. You can check the time when the status of a device changes based on the lastTime parameter.

For example, you receive the following messages in sequence:
  1. Online time: 2018-08-31 10:02:28.195
  2. Offline time: 2018-08-31 10:01:28.195
  3. Offline time: 2018-08-31 10:03:28.195
The preceding three messages indicate that the status of a device changed to offline, online, and then offline.
utcLastTime String The time in UTC when the last communication occurred before the status changed.
clientIp String The public IP address of the device.

Submit device properties

Topic: /${productKey}/${deviceName}/thing/event/property/post

You can use this topic to retrieve the properties that are submitted by devices.

Data format:

{
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"al12345****",
    "deviceName":"deviceName1234",
    "gmtCreate":1510799670074,
    "deviceType":"Ammeter",
    "items":{
        "Power":{
            "value":"on",
            "time":1510799670074
        },
        "Position":{
            "time":1510292697470,
            "value":{
                "latitude":39.9,
                "longitude":116.38
            }
        }
    },
    "checkFailedData":{
        "attribute_8":{
            "time": 1510292697470,
            "value": 715665571,
            "code":6304,
            "message":"tsl parse: params not exist -> attribute_8"
        }
    }
}

The following table describes the parameters.

Parameter Type Description
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
gmtCreate Long The time when the message was generated.
deviceType String The type of the device.
items Object The data that is submitted by the device.
Power String The identifier of the property. For more information about properties, see the TSL model of the product.
If you use the properties of a custom module, the identifier of each property is in the Module identifier:Property identifier format. A colon is used to connect the two parts of this expression. The following example shows the data format if the identifier of a TSL custom module is test:
"items":{
        "test:Power":{
            "value":"on",
            "time":1510799670074
        },
        "test:Position":{
            "time":1510292697470,
            "value":{
                "latitude":39.9,
                "longitude":116.38
            }
        }
    }
Position
attribute_8
checkFailedData Object The data that failed to be verified.
value Subject to the TSL definition The value of the property.
time Long The time when the property was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.
code Integer The error code returned if the data fails to be verified. For more information, see Error codes for devices.
message String The error message returned if the data fails to be verified. The message includes the cause and invalid parameters.

Submit device events

Topic: /${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/post

You can use this topic to retrieve the events that are submitted by devices.

Data format:

{
    "identifier":"BrokenInfo",
    "name":"Damage rate report",
    "type":"info",
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"X5eCzh6****",
    "deviceName":"5gJtxDVeGAkaEztpisjX",
    "gmtCreate":1510799670074,
    "value":{
        "Power":"on",
        "Position":{
            "latitude":39.9,
            "longitude":116.38
        }
    },
    "checkFailedData":{
        "value": {
            "type": "onMapTrace",
            "content": "{\"tid\":\"1313701472\",\"totalCount\":2267,\"traceStart\":2266,\"pointCount\":1,\"traceValue\":\"XQAABAAFAAAAAB0AE6UAB/oAAA==\"}",
            "timestamp": "15970451390162"
        },
        "code":6304,
        "message":"tsl parse: params not exist -> type"
    },
    "time":1510799670074
}

The following table describes the parameters.

Parameter Type Description
identifier String The identifier of the event.
If you use the events of a custom module, the identifier of each property is in the Module identifier:Event identifier format. A colon is used to connect the two parts of this expression. The following example shows the data format if the identifier of a TSL custom module is test:
"test:identifier":"BrokenInfo",
name String The name of the event.
type String The type of the event. For more information about event types, see the TSL model of the product.
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
gmtCreate Long The time when the message was generated.
value Object The parameters of the event.
Power String The name of the event parameter.
Position String The name of the event parameter.
checkFailedData Object The data that failed to be verified.
content String The data that failed to be verified.
timestamp Long The timestamp that was generated when the device submitted the data.
code Integer The error code returned if the data fails to be verified. For more information, see Error codes for devices.
message String The error message returned if the data fails to be verified. The message includes the cause and invalid parameters.
time Long The time when the event was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.

Submit device properties in batches

Topic: /${productKey}/${deviceName}/thing/property/batch/post

You can use this topic to retrieve the properties that are submitted by devices in batches.

Data format:

{
    "productKey": "al12345****",
    "deviceName": "deviceName1234",
    "instanceId": "iot-0***",
    "requestId": "57b144cf-***",
    "payload": {
        "Power": [{
                "value": "on",
                "time": 1524448722000
            },
            {
                "value": "off",
                "time": 1524448722001
            }
        ],
        "WF": [{
                "value": 3,
                "time": 1524448722000
            },
            {
                "value": 4,
                "time": 1524448722009
            }
        ]
    }
}

The following table describes the parameters.

Parameter Type Description
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
instanceId String The ID of the instance to which the device belongs.
requestId String The ID of the request.
payload Object The data that is submitted by the device.
Power String The identifier of the property. For more information about properties, see the TSL model of the product.
If you use the properties of a custom module, the identifier of each property is in the Module identifier:Property identifier format. A colon is used to connect the two parts of this expression. The following example shows the data format if the identifier of a TSL custom module is test:
"payload":{
        "test:Power":[
            {
            "value":"on",
            "time":1510799670074
            },
            {
              "value": "off", 
              "time": 1524448722001
            }],
        "test:WF":[
            {
              "value": 3, 
              "time": 1524448722000
            },
            {
              "value": 4, 
              "time": 1524448722009
            }]
        }
    }
WF
value Subject to the TSL definition The value of the property.
time Long The time when the property was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.

Submit device events in batches

Topic: /${productKey}/${deviceName}/thing/event/batch/post

You can use this topic to retrieve the events that are submitted by devices.

Data format:

{
    "productKey": "al12345****",
    "deviceName": "deviceName1234",
    "instanceId": "iot-0***",
    "requestId": "57b144cf-***",
    "payload": {
        "alarmEvent": [{
                "value": {
                    "Power": "on",
                    "WF": "2"
                },
                "time": 1524448722000
            },
            {
                "value": {
                    "Power": "on",
                    "WF": "2"
                },
                "time": 1524448723000
            }
        ]
    }
}

The following table describes the parameters.

Parameter Type Description
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
instanceId String The ID of the instance to which the device belongs.
requestId String The ID of the request.
payload Object The data that is submitted by the device.
alarmEvent List The identifier of the event.
value Object The parameters of the event.

Examples: Power and WF.

time Long The time when the event was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.

Submit lifecycle changes

Topic: /${productKey}/${deviceName}/thing/lifecycle

You can use this topic to retrieve notifications when devices are created, deleted, enabled, or disabled.

Data format:

{
    "action" : "create|delete|enable|disable",
    "iotId" : "4z819VQHk6VSLmmBJfrf00107e****",
    "productKey" : "al5eCzh****",
    "deviceName" : "5gJtxDVeGAkaEztpisjX",
    "deviceSecret" : "", 
    "messageCreateTime": 1510292739881 
}

The following table describes the parameters.

Parameter Type Description
action String
  • create: creates a device
  • delete: deletes a device
  • enable: enables a device
  • disable: disables a device
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
deviceSecret String The DeviceSecret of the device. This parameter is available only if the action parameter is set to create.
messageCreateTime Integer The timestamp that was generated for the message. Unit: milliseconds.

Submit topology changes

Topic: /${productKey}/${deviceName}/thing/topo/lifecycle

You can use this topic to retrieve notifications when topological relationships between sub-devices and gateways are created or deleted.

Data format:

{
    "action" : "create|delete|enable|disable",
    "gwIotId": "dfaejVQHk6VSLmmBJfrf00107e****",
    "gwProductKey": "al5eCzh****",
    "gwDeviceName": "deviceName1234",
    "devices": [ 
        {
          "iotId": "4z819VQHk6VSLmmBJfrf00107e****",
          "productKey": "ala4Czh****",
          "deviceName": "deviceName1234"
       }
    ],

    "messageCreateTime": 1510292739881 
}

The following table describes the parameters.

Parameter Type Description
action String
  • create: creates a topology
  • delete: deletes a topology
  • enable: enables a topology
  • disable: disables a topology
gwIotId String The ID of the gateway in IoT Platform.
gwProductKey String The ProductKey of the product to which the gateway belongs.
gwDeviceName String The name of the gateway.
devices Object The sub-devices whose topologies changed.
iotId String The ID of each sub-device in IoT Platform.
productKey String The ProductKey of the product to which the sub-device belongs.
deviceName String The name of the sub-device.
messageCreateTime Integer The timestamp that was generated for the message. Unit: milliseconds.

Submit information about detected sub-devices

Topic: /${productKey}/${deviceName}/thing/list/found

In some cases, gateways can detect sub-devices and submit sub-device information. You can use this topic to retrieve the submitted information.

Data format:

{
    "gwIotId":"dfaew9VQHk6VSLmmBJfrf00107e****",
    "gwProductKey":"al12345****",
    "gwDeviceName":"deviceName1234",
    "devices":[
        {
            "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
            "productKey":"alr56g9****",
            "deviceName":"deviceName1234"
        }
    ]
}

The following table describes the parameters.

Parameter Type Description
gwIotId String The ID of the gateway in IoT Platform.
gwProductKey String The ProductKey of the product to which the gateway belongs.
gwDeviceName String The name of the gateway.
devices Object The sub-devices that are detected by the gateway.
iotId String The ID of each sub-device in IoT Platform.
productKey String The ProductKey of the product to which the sub-device belongs.
deviceName String The name of the sub-device.

Submit responses to downstream requests

Topic: /${productKey}/${deviceName}/thing/downlink/reply/message

You can use this topic to retrieve the results that are returned after devices process downstream requests. IoT Platform provides an asynchronous method to send the downstream requests to devices. If errors occur when IoT Platform sends the downstream requests, you can also use this topic to retrieve error messages.

Data format:

{
    "gmtCreate":1510292739881,
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"al12355****",
    "deviceName":"deviceName1234",
    "requestId":1234,
    "code":200,
    "message":"success",
    "topic":"/sys/al12355****/deviceName1234/thing/service/property/set",
    "data":{

    },
    "checkFailedData":{
        "value": {
            "PicID": "15194139"
        },
        "code":6304,
        "message":"tsl parse: params not exist -> PicID"
    }
}

The following table describes the parameters.

Parameter Type Description
gmtCreate Long The timestamp. The time is displayed in UTC.
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
requestId Long The ID of the request.
code Integer The response code that is returned by the device. For more information, see the following Response codes table.
message String The message that is returned by the device.
topic String The information about the topic that is used to send the downstream request.
data Object The data that is returned by the device. If the device returns Alink data, you do not need to parse the data. If the device returns pass-through data, you must parse the data by using a data parsing script.
checkFailedData Object The data that failed to be verified.
value Subject to the TSL definition The property or service parameter whose value failed to be verified.

Example: PicID.

code Integer The error code returned if the data fails to be verified. For more information, see Error codes for devices.
message String The error message returned if the data fails to be verified. The message includes the cause and invalid parameters.
Table 1. Response codes
code message Description
200 success The message returned because the request succeeds.
400 request error The error message returned because an internal error has occurred.
460 request parameter error The error message returned because the request parameter is invalid and the device has failed to verify the parameter.
429 too many requests The error message returned because the maximum number of requests in a specified period is reached.
9200 device not actived The error message returned because the device is not activated.
9201 device offline The error message returned because the device is disconnected from IoT Platform.
403 request forbidden The error message returned because the request is rejected due to overdue payments.

For more information about how to troubleshoot errors, see Error codes for devices.

Submit historical properties

Topic: /${productKey}/${deviceName}/thing/event/property/history/post

You can use this topic to retrieve historical properties that are submitted by devices.

Data format:

{
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"12345****",
    "deviceName":"deviceName1234",
    "gmtCreate":1510799670074,
    "deviceType":"Ammeter",
    "items":{
        "Power":{
            "value":"on",
            "time":1510799670074
        },
        "Position":{
            "time":1510292697470,
            "value":{
                "latitude":39.9,
                "longitude":116.38
            }
        }
    },
    "checkFailedData":{
        "attribute_8":{
            "time": 1510292697470,
            "value": 715665571,
            "code":6304,
            "message":"tsl parse: params not exist -> attribute_8"
        }
    }
}

The following table describes the parameters.

Parameter Type Description
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
gmtCreate Long The time when the message was generated.
deviceType String The type of the TSL feature. For more information, see the TSL model of the product.
items Object The data that is submitted by the device.
Power String The identifier of the property. For more information about properties, see the TSL model of the product.
If you use the properties of a custom module, the identifier of each property is in the Module identifier:Property identifier format. A colon is used to connect the two parts of this expression. The following example shows the data format if the identifier of a TSL custom module is test:
"items":{
        "test:Power":{
            "value":"on",
            "time":1510799670074
        },
        "test:Position":{
            "time":1510292697470,
            "value":{
                "latitude":39.9,
                "longitude":116.38
            }
        }
    }
Position
attribute_8
value Subject to the TSL definition The value of the property.
time Long The time when the property was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.
checkFailedData Object The data that failed to be verified.
code Integer The error code returned if the data fails to be verified. For more information, see Error codes for devices.
message String The error message returned if the data fails to be verified. The message includes the cause and invalid parameters.

Submit historical events

Topic: /${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/history/post

You can use this topic to retrieve historical events that are submitted by devices.

Data format:

{
    "identifier":"BrokenInfo",
    "name":"Damage rate report",
    "type":"info",
    "iotId":"4z819VQHk6VSLmmBJfrf00107e****",
    "productKey":"X5eCzh6****",
    "deviceName":"5gJtxDVeGAkaEztpisjX",
    "gmtCreate":1510799670074,
    "value":{
        "Power":"on",
        "Position":{
            "latitude":39.9,
            "longitude":116.38
        }
    },
    "checkFailedData":{
        "value": {
            "type": "onMapTrace",
            "content": "{\"tid\":\"1313701472\",\"totalCount\":2267,\"traceStart\":2266,\"pointCount\":1,\"traceValue\":\"XQAABAAFAAAAAB0AE6UAB/oAAA==\"}",
            "timestamp": "15970451390162"
        },
        "code":6304,
        "message":"tsl parse: params not exist -> type"
    },
    "time":1510799670074
}

The following table describes the parameters.

Parameter Type Description
identifier String The identifier of the event.
If you use the events of a custom module, the identifier of each property is in the Module identifier:Event identifier format. A colon is used to connect the two parts of this expression. The following example shows the data format if the identifier of a TSL custom module is test:
"test:identifier":"BrokenInfo",
name String The name of the event.
type String The type of the event. For more information about event types, see the TSL model of the product.
iotId String The ID of the device in IoT Platform.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
gmtCreate Long The time when the message was generated.
value Object The parameters of the event.
Power String The name of the event parameter.
Position String The name of the event parameter.
time Long The time when the event was submitted. If the device does not submit a timestamp, the timestamp that is generated when IoT Platform receives the message is used.
checkFailedData Object The data that failed to be verified.
content String The data that failed to be verified.
timestamp Long The timestamp that was generated when the device submitted the data.
code Integer The error code returned if the data fails to be verified. For more information, see Error codes for devices.
message String The error message returned if the data fails to be verified. The message includes the cause and invalid parameters.

Submit the status data of OTA updates

Topic: /${productKey}/${deviceName}/ota/upgrade

You can use this topic to retrieve notifications when OTA updates succeed or fail.

Note If a device has a pending update task and you initiate another batch update task on the device, the latter update task fails. In this case, the notification that is generated when the latter update task fails is not submitted to IoT Platform.

Data format:

{
    "iotId": "4z819VQHk6VSLmmBJfrf00107e****",
    "productKey": "X5eCzh6****",
    "deviceName": "deviceName1234",
    "moduleName": "default",
    "status": "SUCCEEDED|FAILED|CANCELED",
    "messageCreateTime": 1571323748000,
    "srcVersion": "1.0.1",
    "destVersion": "1.0.2",
    "desc": "success",
    "jobId": "wahVIzGkCMuAUE2gDERM02****",
    "taskId": "y3tOmCDNgpR8F9jnVEzC01****"
}

The following table describes the parameters.

Parameter Type Description
iotId String The ID of the device.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
moduleName String The name of the OTA module.
status String The status of the update. Valid values:
  • SUCCEEDED: The update is successful.
  • FAILED: The update failed.
  • CANCELED: The update task is canceled.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.
srcVersion String The firmware version before the update.
destVersion String The firmware version after the update.
desc String The description of the update.
jobId String The ID of the update batch.
taskId String The ID of the device update record.

Submit the progress data of OTA updates

Topic: /${productKey}/${deviceName}/ota/progress/post

You can use this topic to retrieve the progress data of OTA updates.

Data format:

{
    "iotId": "4z819VQHk6VSLmmBJfrf00107e****",
    "productKey": "X5eCzh6****",
    "deviceName": "deviceName1234",
    "moduleName":"default",
    "status":"IN_PROGRESS",
    "step": "90", 
    "messageCreateTime": 1571323748000,
    "srcVersion":"1.0.1",
    "destVersion":"1.0.2",
    "desc": "success",
    "jobId": "wahVIzGkCMuAUE2gDERM02****",
    "taskId": "y3tOmCDNgpR8F9jnVEzC01****"
}

The following table describes the parameters.

Parameter Type Description
iotId String The ID of the device.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
moduleName String The name of the OTA module.
status String The status of the update. Set the value to IN_PROGRESS.
step Integer The progress of the update.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.
srcVersion String The firmware version before the update.
destVersion String The firmware version after the update.
desc String The description of the update.
jobId String The ID of the update batch.
taskId String The ID of the device update record.

Submit OTA module versions

Topic: /${productKey}/${deviceName}/ota/version/post

You can use this topic to retrieve OTA module versions that are submitted by devices. If the submitted versions are different from the previous versions, the messages that are sent to the topic are forwarded.

Data format:

{
    "iotId": "4z819VQHk6VSLmmBJfrf00107e****",
    "deviceName": "deviceName1234",
    "productKey": "X5eCzh6****",
    "moduleName": "BarcodeScanner",
    "moduleVersion": "1.0.3",
    "messageCreateTime": 1571323748000
}

The following table describes the parameters.

Parameter Type Description
iotId String The ID of the device.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
moduleName String The name of the module.
moduleVersion String The version number of the module.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.

Submit the status data of OTA update batches

Topic: /${productKey}/${packageId}/${jobId}/ota/job/status

You can use this topic to retrieve the status data of OTA update batches.

Data format:

{
    "productKey": "X5eCzh6****",
    "moduleName": "BarcodeScanner",
    "packageId": "wahVIzGkCMuAUE2***",
    "jobId": "wahVIzGkCMuAUE2gDERM02****",
    "status": "IN_PROGRESS",
    "messageCreateTime": 1571323748000
}

The following table describes the parameters.

Parameter Type Description
productKey String The ProductKey of the product to which the device belongs.
moduleName String The name of the module.
packageId String The ID of the update package. The value of this parameter is the same as the value of the FirmwareId parameter that is returned when you call the CreateOTAFirmware operation to create an update package.
jobId String The ID of the update batch.
status String The status of the update batch. Valid values:
  • PLANNED: The update batch is not started.
  • IN_PROGRESS: The update batch is running.
  • COMPLETED: The update is complete.
  • CANCELED: The update is canceled.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.

Submit device tag changes

Topic: /${productKey}/${deviceName}/thing/deviceinfo/update

You can use this topic to retrieve notifications when a device tag is changed.

Data format:

{
  "action": "UPDATE|DELETE|DELETEALL"
  "iotId": "4z819VQHk6VSLmmBJfrf00107e****",
  "productKey": "X5eCzh6****",
  "deviceName": "deviceName1234",
  "deletedAttrKeyList": ["abc", "def", "rng"],
  "value": [
    {
      "attrKey": "tagKey",
      "attrValue": "tagValue"
    }
  ],
  "messageCreateTime": 1510799670074
}

The following table describes the parameters.

Parameter Type Description
action String The type of the tag change. Valid values:
  • UPDATE: The tag is updated or created.
  • DELETE: The tag is deleted.
  • DELETEALL: All tags are cleared.
iotId String The ID of the device.
productKey String The ProductKey of the product to which the device belongs.
deviceName String The name of the device.
deletedAttrKeyList List The keys of the deleted tags.

This parameter is available only if the action parameter is set to DELETE.

value List The data of the tag.
attrKey String The key of the tag.
attrValue String The value of the tag.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.

Submit device job changes

Topic: /sys/uid/${uid}/job/${jobId}/lifecycle

You can use this topic to retrieve the status changes of device jobs. These device jobs include jobs that are used to set multiple device properties, jobs that are used to call multiple device services, and custom jobs.

Replace ${uid} with your Alibaba Cloud account ID. To view the account ID, log on to the IoT Platform console and click the profile picture in the upper-right corner of the page. The account ID is displayed on the Security Settings page.

Data format:

{
    "jobId": "4z819VQHk6VSLmm***ee200",
    "jobType": "CUSTOM_JOB",
    "status": "INITIALIZING",
    "messageCreateTime": 1510292739881
}

The following table describes the parameters.

Parameter Type Description
jobId String The ID of the job.
jobType String The type of the job. Valid values:
  • SET_PROPERTY: a job that is used to set multiple device properties.
  • INVOKE_SERVICE: a job that is used to call multiple device services.
  • CUSTOM_JOB: a custom job.
status String The status of the job. Valid values:
  • INITIALIZING: The job is being initialized.
  • WAITING: The job is pending. The job needs to be scheduled.
  • IN_PROGRESS: The job is running.
  • COMPLETED: The job is completed.
  • CANCELLING: The job is being canceled.
  • CANCELED: The job is canceled.
  • REMOVING: The job is being deleted.
messageCreateTime Long The timestamp that was generated for the message. Unit: milliseconds.