Configuration Rules

Gets a list of configuration Rules

get

This endpoint is used to fetch all the configuration Rules 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_rules/
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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
post
/ux/nccm/configuration_rules/
201Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/nccm/configuration_rules/{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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
put
/ux/nccm/configuration_rules/{id}/
200Success
delete

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
delete
/ux/nccm/configuration_rules/{id}/
204

No response body

No content

Return JSON for Configuration Rule

post

This endpoint is to Import Text From OLD NCCM for Configuration Rule.

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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/import-txt/
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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/is_disabled/
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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/is_enabled/
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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/multidelete/
200Success
get

API endpoint that allows users to be viewed or edited.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/nccm/configuration_rules/options/
200Success

Return JSON for Configuration Rule

post

Save Imported Text From OLD NCCM for Configuration Rule.

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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/save-txt/
200Success

Return JSON for Configuration Rule

post

This endpoint is to Import Json for Configuration Rule.

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
rule_config_severitystringRead-onlyRequired
rule_typestringRead-onlyRequired
match_criteriastringRead-onlyRequired
statusstringRead-onlyRequired
rollback_typestringRead-onlyRequired
on_violation_performstringRead-onlyRequired
remedy_configuredstringRead-onlyRequired
rule_descriptionstringRead-onlyRequired
ruleidstring · max: 25Required
rule_display_idstringRequired
organizationstring · max: 25Required
last_update_timestring · date-timeOptional
creation_timestring · date-timeOptional
created_bystringOptional
modified_bystringOptional
is_deletedbooleanOptional
is_privatebooleanOptional
creatorstringOptional
namestringOptional
descriptionstringOptional
compliance_standardstringOptional
compliance_detailsstringOptional
rule_execution_typeintegerOptional
activationbooleanOptionalDefault: true
is_enabledbooleanOptionalDefault: true
vendorstringOptional
os_typestringOptional
is_editablebooleanOptional
device_typestringOptional
config_typestringOptional
inv_commandsstringOptional
other_configsstringOptional
config_script_idstringOptional
config_script_commandsstringOptional
nw_reviewsstringOptional
executionbooleanOptional
rule_start_timestring · date-timeOptional
rule_end_timestring · date-timeOptional
severityintegerOptional
alarm_msgstringOptional
notifier_idstringOptional
rollback_script_idstringOptional
rollback_script_commandsstringOptional
rollback_script_adv_commandsstringOptional
rollback_commentsstringOptional
continue_nextcommand_on_failurebooleanOptional
rule_infostringOptional
template_idstringOptional
os_versionstringOptional
Responses
chevron-right
200Success
application/json
post
/ux/nccm/configuration_rules/validate-json/
200Success

Last updated