Updated on 2025-03-26 GMT+08:00

Custom Command Delivery Devices

Function

This API is used to customize a command delivery device.

URI

POST /v2/{project_id}/link/instances/{instance_id}/devices/customize-commands

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID. The default value is default for compatibility with 20.0.Project ID. For details about how to get the project ID, see "Appendix" > "Obtaining a Project ID" in this document.

instance_id

Yes

String

Instance ID. The default value is default for compatibility with 20.0.

Table 2 Query Parameters

Parameter

Mandatory

Type

Description

topic

Yes

String

Custom command delivery topic

app_id

Yes

String

Application ID

device_id

Yes

String

Device client ID, which is the unique device ID generated by the platform. The device name, client ID, and device ID can be used for joint query. Too many devices may lead to query timeouts. You are advised to specify one condition with more key words.

qos

No

String

Service quality. The default value is 0. Only 0 and 1 are allowed.

Request Parameters

Table 3 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.

Table 4 Request body parameters

Parameter

Mandatory

Type

Description

SendCustomizeCommandRequestBody

No

String

This API is used to customize a command delivery body.

Response Parameters

Status code: 201

Table 5 Response body parameters

Parameter

Type

Description

code

String

Status code of command delivery response

msg

String

Content of command delivery

Status code: 400

Table 6 Response body parameters

Parameter

Type

Description

error_code

String

System error code, which is the detailed error code of HTTP error codes 4xx and 5xx.

error_msg

String

Error description.

request_id

String

Message ID.

Status code: 404

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

System error code, which is the detailed error code of HTTP error codes 4xx and 5xx.

error_msg

String

Error description.

request_id

String

Message ID.

Status code: 500

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

System error code, which is the detailed error code of HTTP error codes 4xx and 5xx.

error_msg

String

Error description.

request_id

String

Message ID.

Example Requests

Create a device with protocol type as MQTT, product type as common, and device status as enabled.

{
  "aa" : 123
}

Example Responses

Status code: 201

Created

{
  "msg" : "SENDMESSAGE_SUCCESS.",
  "code" : "iot.api.device.command.post.service.sendMessage.success"
}

Status code: 400

Bad Request

{
  "error_code" : "SCB.00000000",
  "error_msg" : "Parameter is not valid for operation [romalink.link-device.save]. Parameter is [parent_device_id]. Processor is [body].",
  "request_id" : "cb39e78a-afd3-4e04-901d-70468b1c23dc-1619602712496-cnnorth7a-P-romalink-service01"
}

Status code: 404

Not Found

{
  "error_code" : "ROMA.00110006",
  "error_msg" : "The resource does not exist. Check whether the resource ID ff38023c-0854-4779-847d-72528e1f5da1 is correct.",
  "request_id" : "624c8be1-39b6-47b7-941d-c159aced368a-1619602544650-cnnorth7a-P-romalink-service01"
}

Status code: 500

Internal Server Error

{
  "error_code" : "ROMA.00110002",
  "error_msg" : "The instance does not exist. project_id: 397cd10b30544c588b2f4a56d83856c4, instance_id: f3bb386a-23ec-47aa-9943-4c60ac658611",
  "request_id" : "c8c06d0a-be92-4fdf-9d10-bc20131ab158-1619593104919-cnnorth7a-P-romalink-service01"
}

Status Codes

Status Code

Description

201

Created

400

Bad Request

404

Not Found

500

Internal Server Error

Error Codes

See Error Codes.