Citrix ADM NITRO API Reference

ns_filterpolicy_template

June 20, 2023

Contributed by:

Configuration for Citrix ADC Filter Policy Configure Task resource.

Properties

(click to see Operations )

Name	Data Type	Permissions	Description
priority		Read-write	Policy Priority.
device_groups	<String[]>	Read-write	Device Group Array on which for which template is applied.
name		Read-write	Name of Policy.
variables	<variable_values[]>	Read-write	Values of Variables used in commands of the configuration template.
state		Read-write	State of the Policy: enabled/disabled.
devices	<String[]>	Read-write	Device IP Address Array on which template is applied.
actionType		Read-write	Action Type of the Policy.
actionName		Read-write	Action Name of the Policy.
expression		Read-write	Expression of the Policy.

Operations

(click to see Properties )

ADD
GET (ALL)

Some options that you can use for each operations:

Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes

If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

To do this, you must specify the username and password in the request header of the NITRO request as follows:

X-NITRO-USER: <username>

X-NITRO-PASS: <password>

Note: In such cases, make sure that the request header DOES not include the following:

Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

*Note:* Mandatory parameters are marked in red and placeholder content is marked in green

The following parameters can be used in the nitro request : onerror <String_value>

Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.

Default value: EXIT

Possible values = EXIT, CONTINUE

add

URL: https://<MGMT-IP>/nitro/v2/config/ns_filterpolicy_template?onerror=<String_value> HTTPS Method: POST

Request Headers: Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"ns_filterpolicy_template": {
"priority":<Integer_value>,
"state":<String_value>,
"actionName":<String_value>,
"expression":<String_value>,
"name":<String_value>,
"devices":<String_value[]>,
"variables":[{
<b>"name":<String_value></b>,
"parent_id":<String_value>,
"default_value":<String_value>,
"id":<String_value>,
"values_enum_db":<String_value>,
"parent_name":<String_value>,
"value":<String_value>,
"description":<String_value>,
"type":<String_value>,
"valuex":<String_value>,
"device_values":[{
"value":<String_value>,
"id":<String_value>,
"device":<String_value>,
"device_group":<String_value>,
"valuex":<String_value>}],
"display_name":<String_value>}],
"actionType":<String_value>,
"device_groups":<String_value[]>}}

 

Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "ns_filterpolicy_template":[{
"priority":<Integer_value>,
"device_groups":<String_value>,
"name":<String_value>,
"variables":[{
"device_values_mapping":<String_value>,
"parent_name":<String_value>,
"value":<String_value>,
"name":<String_value>,
"valuex":<String_value>,
"display_name":<String_value>,
"description":<String_value>,
"device_values":[{
"parent_name":<String_value>,
"value":<String_value>,
"id":<String_value>,
"valuex":<String_value>,
"device_group":<String_value>,
"device":<String_value>,
"parent_id":<String_value>}],
"parent_id":<String_value>,
"default_value":<String_value>,
"id":<String_value>,
"type":<String_value>,
"values_enum_db":<String_value>}],
"state":<String_value>,
"devices":<String_value>,
"actionType":<String_value>,
"actionName":<String_value>,
"expression":<String_value>}]}

 

get (all)

URL: https://<MGMT-IP>/nitro/v2/config/ns_filterpolicy_template Query-parameters:

filter https://<MGMT-IP>/nitro/v2/config/ns_filterpolicy_template ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of ns_filterpolicy_template resources configured on the system. You can set a filter on any property of the resource.

pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/ns_filterpolicy_template ?pagesize=#no;pageno=#no Use this query-parameter to get the ns_filterpolicy_template resources in chunks.

count https://<MGMT-IP>/nitro/v2/config/ns_filterpolicy_template ?count=yes Use this query-parameter to get the count of ns_filterpolicy_template resources.

HTTPS Method: GET

Request Headers: Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "ns_filterpolicy_template":[{
"priority":<Integer_value>,
"device_groups":<String_value>,
"name":<String_value>,
"variables":[{
"device_values_mapping":<String_value>,
"parent_name":<String_value>,
"value":<String_value>,
"name":<String_value>,
"valuex":<String_value>,
"display_name":<String_value>,
"description":<String_value>,
"device_values":[{
"parent_name":<String_value>,
"value":<String_value>,
"id":<String_value>,
"valuex":<String_value>,
"device_group":<String_value>,
"device":<String_value>,
"parent_id":<String_value>}],
"parent_id":<String_value>,
"default_value":<String_value>,
"id":<String_value>,
"type":<String_value>,
"values_enum_db":<String_value>}],
"state":<String_value>,
"devices":<String_value>,
"actionType":<String_value>,
"actionName":<String_value>,
"expression":<String_value>}]}

 

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

ns_filterpolicy_template

June 20, 2023

Contributed by:

ns_filterpolicy_template

Properties

Operations

add

get (all)

In this article