Configuration Trigger

Gets a list of configuration trigger

get

This endpoint is used to fetch all the configuration trigger 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/nccm/configuration_trigger/
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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
post
/ux/nccm/configuration_trigger/
201Success

Retrive the configuration trigger with given id

get

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

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/nccm/configuration_trigger/{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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
put
/ux/nccm/configuration_trigger/{id}/
200Success
delete

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/nccm/configuration_trigger/{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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/add_trigger/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/nccm/configuration_trigger/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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/multi-delete/
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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/review/
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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/save_csv_data/
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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/saved_imported/
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
modified_by_namestringRead-onlyRequired
creationtimestringRead-onlyRequired
last_update_timestringRead-onlyRequired
trigger_commandsstringRead-onlyRequired
parser_textstringRead-onlyRequired
trigger_typestringRead-onlyRequired
trigger_parser_typestringRead-onlyRequired
created_by_profilestringRead-onlyRequired
modified_by_profilestringRead-onlyRequired
trigger_idstringRequired
trigger_namestringOptional
organizationstring · max: 25Required
descriptionstringOptional
vendorstringOptional
os_namestringOptional
is_privatebooleanOptional
trigger_column_indexintegerOptionalDefault: 1
created_byintegerOptional
modified_byintegerOptional
is_deletedbooleanOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_trigger/validate_csv/
200Success

Last updated