Administrator Guide

Status Error Codes Description
405 Method Not
Allowed
The HTTP method specified in the request (DELETE, GET, HEAD, PATCH, POST,
PUT) is not supported for this resource.
406 Not
Acceptable
The resource this request identifies is not capable of generating the requested
representation, specified in the “Accept” header or in the “format” query parameter.
409 Conflict This code is used if a request tries to create a resource that already exists.
415 Unsupported
Media Type
The format of the request is not supported.
500 Internal Error The server encountered an unexpected condition which prevented it from fulfilling
the request.
501 Not
Implemented
The server does not (currently) support the functionality required to fulfill the
request.
503 Unavailable The server is currently unable to handle the request because the resource is being
used by someone else or is temporarily overloaded.
REST API — Protocol Data Unit (PDU) Structure
The following features are supported to configure the REST API.
• Physical interface
• Logical interface
• BGP
• Infrastructure
• Miscellaneous
Each node is printed as: <status> <flags> <name> <opts> <type>.
• <status> is one of the following:
– + for current
– x for deprecated
– o for obsolete
• <flags> is one of the following:
– rw for configuration data
– ro for non-configuration data
– -x for rpcs
– -n for notifications
• <name> is the name of the node.
– (<name>) refers that the node is a choice node
– :(<name>) refers that the node is a case node
– -x for rpcs.
NOTE: If the node is augmented into the tree from another module, the name is printed as
<prefix>:<name>.
REST API
133