Pushing Device Service Capability Addition Notifications

Typical Scenario

After an NA subscribes to device service capability addition notifications (the notification type is deviceCapabilitiesAdded) on the IoT platform, the IoT platform sends a notification message to the NA when a device profile file is added on the IoT platform.

API Function

This API is used by the IoT platform to push notification messages to an NA that has subscribed to device service capability addition notifications.

Note

The NA must return a response code after receiving a message pushed by the IoT platform.

API Prototype

Method	POST
URL	The URL is determined by callbackUrl in the subscription request sent by the NA.
Transport Protocol	HTTPS/HTTP

Request Parameters

Parameter	Mandatory or Optional	Type	Location	Description
notifyType	Mandatory	String	body	Indicates the notification type. The value is deviceCapabilitiesAdded.
appId	Mandatory	String	body	Identifies an application that can be accessed on the IoT platform. The value of this parameter is allocated by the IoT platform when the application is created on the platform. Set this parameter to the value of appId of the authorized application.
deviceType	Mandatory	String	body	Indicates the device type.
manufacturerName	Mandatory	String	body	Indicates the name of the manufacturer of the device model.
manufacturerId	Mandatory	String	body	Identifies the manufacturer of the device model.
model	Mandatory	String	body	Indicates the device model.
protocolType	Mandatory	String	body	Indicates the protocol used by the device.

Response Parameters

Status Code: 200 OK

Request Example

Method: POST
Request: {callbackUrl}
Header:
Content-Type: application/json
Body:
{
  "notifyType": "deviceCapabilitiesAdded",
  "appId": "*****",
  "deviceType": "*************",
  "manufacturerName": "wulian",
  " manufacturerId ": "*************",
  "model": "*************",
  "protocolType": "zigbee"
}