The content query parameter controls how descendant nodes of the requested data nodes are processed in the reply:

• Must be supported by the server.

• If not present in URI, the default value is: all. Allowed only for GET/HEAD method.

  A "400 Bad Request" status-line is returned if used for other methods or resource types.

Examples for allowed values are:

1. https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native?content=config

2. https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native?content=nonconfig’

Query Parameters (Fields)

• The depth-query parameter is used to limit the depth of subtrees returned by the server.

• The value of the "depth" parameter is either an integer between 1 and 65535 or the string "unbounded".

• Supported if present in the capability URI.

• If not present in URI, the default value is: “unbounded”.

• Only allowed for GET/HEAD method.

  A 400 Bad Request status-line is returned if used for other methods or resource types.

Examples:

1)‘https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native?content=config&depth=65535’

2)‘https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native?content=nonconfig&depth=0’

>>> resp

<Response [400]>

>>> resp.text

'{"errors": {"error": [{"error-message": "invalid value for depth query parameter", "error-tag": "malformed-message", "error-type": "application"}]}}\n'

>>> 

Examples:

• • The "fields" query parameter is used to optionally identify data nodes within the target resource to be retrieved in a GET method.

• Supported if present in the capability URI.

  Allowed only for GET/HEAD method.

• A "400 Bad Request" status-line is returned if used for other methods or resource types.

• A value of the "fields" query parameter matches the following rule:

  fields-expr = path "(" fields-expr ")" / path ";" fields-expr / path path = api-identifier [ "/" path ]

• 1. ";" is used to select multiple nodes.

  2. Parentheses are used to specify sub-selectors of a node. Note that there is no path separator character "/" between a "path" field and a left parenthesis character "(".

  3. "/" is used in a path to retrieve a child node of a node.

• A value of the "fields" query parameter matches the following rule:

  fields-expr = path "(" fields-expr ")" / path ";" fields-expr / path path = api-identifier [ "/" path ]

• 1. ";" is used to select multiple nodes.

  2. Parentheses are used to specify sub-selectors of a node. Note that there is no path separator character "/" between a "path" field and a left parenthesis character "(".

  3. "/" is used in a path to retrieve a child node of a node.

Examples:

1. Server module information: 'https://10.85.116.59:443/restconf/data?fields=ietf-yang-library:modules-state/module(name;revision;schema;namespace)‘

2. Name and IP: ‘https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/interface?fields=GigabitEthernet/ip/address/primary;name'

Query Parameters (Point)

• The "point" query parameter uses to specify the insertion point for a data resource that is being created or moved within an ordered-by user list or leaf-list.

• Must be supported by the server:

  • Only allowed for POST and PUT methods.

    The value of the "point" parameter is a string that identifies the path to the insertion point object. The format is the same as a target resource URI string.

  Examples:

  PUT: ‘https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/privilege/exec/level=2/command-list=show%20terminal?insert=after&point=%2FCisco-IOS-XE-native%3Anative%2Fprivilege%2Fexec%2Flevel%3d2%2Fcommand-list=show%20clock’
  
  {
  
    "Cisco-IOS-XE-native:command-list": [
  
      {
  
        "command": "show terminal"
  
      }
  
    ]
  
  

Query Parameters (with defaults)

The 'with-defaults' query parameter is used to specify how information about default data nodes is returned in response to GET requests on data resources. Default basic-mode in capability is explicit.

• The "point" query parameter uses to specify the insertion point for a data resource that is being created or moved within an ordered-by user list or leaf-list.

  Examples:

  Sync default settings (error): ‘https://10.85.116.59:443/restconf/data/cisco-self-mgmt:netconf-yang/cisco-ia:cisco-ia/cisco-ia:logging/cisco-ia:sync-log-level?with-defaults=report-all’
  Intelligent sync (true): 'https://10.85.116.59:443/restconf/data/cisco-self-mgmt:netconf-yang/cisco-ia:cisco-ia/cisco-ia:intelligent-sync?with-defaults=report-all'