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
- application/json
Path Parameters
-
app-id: string
Unique identifier of the application
Root Schema : DeviceModelImpl_create
Type:
Show Source
object
-
actions(optional):
array actions
Property description was not set
-
attributes(optional):
array attributes
Property description was not set
-
description(optional):
string
Property description was not set
-
formatObjects(optional):
array formatObjects
Property description was not set
-
formats:
array formats
Property description was not set
-
name:
string
Property description was not set
-
uRN:
string
Property description was not set
Nested Schema : DeviceModelActionModel_create
Type:
Show Source
object
-
alias(optional):
string
Property description was not set
-
argType(optional):
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
-
arguments(optional):
array arguments
Property description was not set
-
description(optional):
string
Property description was not set
-
name:
string
Property description was not set
-
range(optional):
string
Property description was not set
Nested Schema : DeviceModelActionArgumentModel_create
Type:
Show Source
object
-
description(optional):
string
Property description was not set
-
name:
string
Property description was not set
-
range(optional):
string
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
Nested Schema : DeviceModelAttributeModel_create
Type:
Show Source
object
-
alias:
string
Property description was not set
-
description:
string
Property description was not set
-
name:
string
Property description was not set
-
range:
string
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
-
writable:
boolean
Property description was not set
Nested Schema : MessageFormatModel_create
Type:
Show Source
object
-
description:
string
Property description was not set
-
deviceModel:
string
Property description was not set
-
name:
string
Property description was not set
-
type:
string
One of [DATA, ALERT, EXPLORATION, EXPLORATION_DATA, EXPLORATION_ALERT, IACS_DATA, IACS_ALERT].
-
uRN:
string
Property description was not set
-
value:
object MessageFormatValue_create
Nested Schema : MessageFormatValue_create
Type:
Show Source
object
-
fields:
array fields
Property description was not set
Nested Schema : MessageFormatField_create
Type:
Show Source
object
-
name:
string
Property description was not set
-
optional:
boolean
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
Response
Supported Media Types
- application/json
- application/vnd.oracle.resource+json;type=singular
202 Response
Successfully processed.
Root Schema : DeviceModelImpl_receive
Type:
Show Source
object
-
actions:
array actions
Property description was not set
-
attributes:
array attributes
Property description was not set
-
created:
integer
Property description was not set
-
createdAsDate:
integer
Property description was not set
-
description:
string
Property description was not set
-
draft:
boolean
Property description was not set
-
formatObjects:
array formatObjects
Property description was not set
-
lastModified:
integer
Property description was not set
-
lastModifiedAsDate:
integer
Property description was not set
-
name:
string
Property description was not set
-
system:
boolean
Property description was not set
-
uRN:
string
Property description was not set
-
userLastModified:
string
Property description was not set
Nested Schema : DeviceModelActionModel_receive
Type:
Show Source
object
-
alias:
string
Property description was not set
-
argType:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
-
arguments:
array arguments
Property description was not set
-
description:
string
Property description was not set
-
name:
string
Property description was not set
-
range:
string
Property description was not set
Nested Schema : DeviceModelActionArgumentModel_receive
Type:
Show Source
object
-
description:
string
Property description was not set
-
name:
string
Property description was not set
-
range:
string
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
Nested Schema : DeviceModelAttributeModel_receive
Type:
Show Source
object
-
alias:
string
Property description was not set
-
description:
string
Property description was not set
-
name:
string
Property description was not set
-
range:
string
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
-
writable:
boolean
Property description was not set
Nested Schema : MessageFormatModel_receive
Type:
Show Source
object
-
description:
string
Property description was not set
-
deviceModel:
string
Property description was not set
-
explorationId:
string
Property description was not set
-
name:
string
Property description was not set
-
severity:
string
Property description was not set
-
sourceId:
string
Property description was not set
-
sourceType:
string
One of [UNKNOWN, DEVICE_MODEL, EXPLORATION, ANALYTICS].
-
type:
string
One of [DATA, ALERT, EXPLORATION, EXPLORATION_DATA, EXPLORATION_ALERT, IACS_DATA, IACS_ALERT].
-
uRN:
string
Property description was not set
-
value:
object MessageFormatValue_receive
Nested Schema : MessageFormatValue_receive
Type:
Show Source
object
-
fields:
array fields
Property description was not set
Nested Schema : MessageFormatField_receive
Type:
Show Source
object
-
name:
string
Property description was not set
-
optional:
boolean
Property description was not set
-
type:
string
One of [STRING, NUMBER, BOOLEAN, INTEGER, DATETIME, URI].
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.