Cisco D9800 Reference Manual page 148

Input Configuration Command
Command Detail
POST Syntax
Table 133: URI Parameters (extension to the Command URL separated by /)
URI Parameter
default
URI Query/Set Arguments (possible fields and values preceded by ? and separated by &): N/A
Input XML Field Descriptions:
The XML parameters are as described in each of the following input configuration API sections Arguments
options
Output Fields:
Output fields returned in GET results are the same names used for the possible Arguments when appending
each possible URI Parameter to this command.
POST (Settings Write) Examples:
Input with invalid setting (Setting Parameters using XML body data from command line):
curl -k -X POST -H "X-SESSION-ID: $token" --header "Content-type:application/xml" -d
"<input><rf><port>1</port><act>Yes</act><dnlkfreq>3.40></dnlkfreq></rf><rf><port>2</port><dnlkfreq>3.40</dnlkfreq></rf></input>"
"https://192.168.0.1/ws/v2/service_cfg/input"
Expected output (values are for example purposes only) when validation of input parameter(s) fail:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<response><code>10</code><result>failure</result><message>the downlink frequency band did
not match the LO frequency band</message></response>
Input with valid setting (Setting Parameters using XML body data from command line):
curl -k -X POST -H "X-SESSION-ID: $token" --header "Content-type:application/xml" -d
"<input><rf><port>1</port><act>Yes</act><dnlkfreq>12.31></dnlkfreq></rf><rf><port>2</port><dnlkfreq>3.40</dnlkfreq></rf></input>"
"https://192.168.0.1/ws/v2/service_cfg/input"
Expected output (values are for example purposes only) when validation of input parameter(s) pass:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<response><code>10</code><result>success</result><message></message></response>
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
136
Description
Either (using body data from command line)
POST –-header "Content-type:application/xml" –d
"<input>some_XML_body_data</input>"
"https://192.168.0.1/ws/v2/service_cfg/input"
OR (using body data from XML file)
POST –-header "Content-type:application/xml" –d
@"C:/your_path/input.xml" "https://192.168.0.1/ws/v2/service_cfg/input"
Description
By default (no additional URL extension), all data is
returned in a GET, and any data may be set in a
POST.
See following command sections for API syntax that
extends this command URL and allows returning or
setting a categorized subset of the fields.
API Definitions