Create a Device Model and associate it with the Application

post

/iot/api/v2/apps/{app-id}/deviceModels

This resource allows to create a Device Model and associate it with an Application

Request

Supported Media Types
Path Parameters
Body ()
Root Schema : DeviceModelImpl_create
Type: object
Show Source
Nested Schema : actions
Type: array
Property description was not set
Show Source
Nested Schema : attributes
Type: array
Property description was not set
Show Source
Nested Schema : formatObjects
Type: array
Property description was not set
Show Source
Nested Schema : formats
Type: array
Property description was not set
Show Source
Nested Schema : DeviceModelActionModel_create
Type: object
Show Source
Nested Schema : arguments
Type: array
Property description was not set
Show Source
Nested Schema : DeviceModelActionArgumentModel_create
Type: object
Show Source
Nested Schema : DeviceModelAttributeModel_create
Type: object
Show Source
Nested Schema : MessageFormatModel_create
Type: object
Show Source
Nested Schema : MessageFormatValue_create
Type: object
Show Source
Nested Schema : fields
Type: array
Property description was not set
Show Source
Nested Schema : MessageFormatField_create
Type: object
Show Source
Back to Top

Response

Supported Media Types

202 Response

Successfully processed.
Body ()
Root Schema : DeviceModelImpl_receive
Type: object
Show Source
Nested Schema : actions
Type: array
Property description was not set
Show Source
Nested Schema : attributes
Type: array
Property description was not set
Show Source
Nested Schema : formatObjects
Type: array
Property description was not set
Show Source
Nested Schema : DeviceModelActionModel_receive
Type: object
Show Source
Nested Schema : arguments
Type: array
Property description was not set
Show Source
Nested Schema : DeviceModelActionArgumentModel_receive
Type: object
Show Source
Nested Schema : DeviceModelAttributeModel_receive
Type: object
Show Source
Nested Schema : MessageFormatModel_receive
Type: object
Show Source
Nested Schema : MessageFormatValue_receive
Type: object
Show Source
Nested Schema : fields
Type: array
Property description was not set
Show Source
Nested Schema : MessageFormatField_receive
Type: object
Show Source

400 Response

Bad Request. The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

401 Response

Unauthorized. The request requires user authentication.

403 Response

Forbidden. The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.

404 Response

Not Found. The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

406 Response

Request Not Acceptable. The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

415 Response

Unsupported Media Type. The request entity has a media type which the server or resource does not support.
Back to Top