Table 5 Generic WSAPI code Member Status and Error Codes (continued)
DescriptionHTTP CodeAPI Error CodeAPI Error
ref member contains the
name of the member.
Invalid HTTP header
syntax.
400 Bad Request62INV_HTTP_HEADER
A request body contains
a sequence of characters
400 Bad Request63INV_UTF
that is invalid for the
supported UTF encodings.
A POST request is missing
a JSON request body.
400 Bad Request64INV_INPUT_NO_REQ
The request line (first line)
of an HTTP request does
400 Bad Request65INV_HTTP_REQ
not comply with the form
specified for
“Request-Line” in RFC
2616.
The URI is not absolute,
contains characters not
400 Bad Request66INV_URI
allowed in a URI, contains
invalid percent encoding,
or, after percent
decoding, contains an
invalid UTF-8 character
sequence.
An HTTP POST request
contains an action
400 Bad Request67INV_POST_ACTION
member with an invalid
value.
Services that the system
depends on in order to
503 Service
Unavailable
68SYS_SVC_NOT_READY
process the requested
operation are not ready.
Input contains one or
more illegal characters.
400 Bad Request69INV_INPUT_ILLEGAL_CHAR
System is not licensed for
this feature or
functionality.
403 Forbidden70UNLICENSED_FEATURE
A system service on which
the API server depends
500 Internal
Server Error
95SYSTEM_ERR
has returned an
unexpected error,
preventing the API server
from fulfilling the request.
(Since WSAPI 1.2)
Operation-specific status and error codes for the WSAPI are described in Table 6 (page 20).
HTTP Status and Error Codes 19
To Next Page
Loading...
