Device Template

Gets a list of device_template

get

This endpoint is used to fetch all the device_template in the current organization

Authorizations
AuthorizationstringRequired
Query parameters
items_per_pageintegerRequired

Items Per Page

pageintegerRequired

Page Number

reversebooleanOptional

Sorting Order

sortstringOptional

Sorting Key

Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/
200Success

Creates a new device_template

post

This endpoint is used to save a new device_template for the current organization

Authorizations
AuthorizationstringRequired
Body
Other propertiesanyOptional
Responses
post
/ux/ims/device-template/
201

No response body

No content

Gets a device_template details with the given id

get

This endpoint is used to fetch a device_template in the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/{id}/
200Success
put

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
put
/ux/ims/device-template/{id}/
200Success

Deletes the device_template with given id

delete

This endpoint is used to delete an existing device_template for the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/ims/device-template/{id}/
204

No response body

No content

post

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/ims/device-template/create-templates/
200Success
post

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/ims/device-template/csv_cols/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/download_csv/
200Success
post

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/ims/device-template/multidelete/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/options/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/res-config-options/
200Success
post

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/ims/device-template/sys-object-resync/
200Success
post

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
created_by_namestringRead-onlyRequired
device_iconstringRead-onlyRequired
sys_idstringRequired
sysobjectidstringRequired
organizationstringRequired
productstringOptional
vendorstringOptional
device_typestringOptional
os_typestringOptional
modelstringOptional
seriesstringOptional
is_deletedbooleanOptional
modified_bystringOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
created_bystringOptional
vendor_iconstringOptional
os_iconstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/ims/device-template/upload-csv/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/ims/device-template/verify-oid-exists/
200Success

Last updated