HP 3PAR StoreServ 7400 2-node HP 3PAR Web Service API 1.2 Developer's - Page 18

continued

Page 18 highlights

Table 5 Generic WSAPI code Member Status and Error Codes (continued) API Error API Error Code HTTP Code Description SVC_UNAVAIL 31 503 Service The server has reached its Unavailable maximum number of connections. IN_USE 34 409 Conflict The resource is in use. UNSUP_REPRESENTATION 35 UNSUP_LANGUAGE 36 NON_EXISTENT_DOMAIN 38 INV_INPUT_WRONG_TYPE 39 INV_INPUT_MISSING_REQUIRED 40 UNSUP_CONTENT 51 INV_INPUT_NOT_JSON_OBJ 52 INV_URL_PERCENT_ENCODING 56 INV_INPUT_EXCEEDS_LENGTH 57 JSON_SYNTAX_ERR 60 JSON_NOT_SUPPORTED 61 406 Not Acceptable The representation specified in client's HTTP Accept header is not supported. 406 Not Acceptable The language specified in client's HTTP Accept-Language header is not supported. 404 Not Found The domain does not exist. 400 Bad Request A JSON input object contains a name-value pair where the type of the value differs from what is expected (e.g. a number is found where a string is expected). The HTTP ref member contains the name of the name-value pair. 400 Bad Request A JSON input object is missing a required name-value pair. The HTTP ref member contains the expected name. 415 Unsupported Media Type Unsupported content (e.g., as specified in the HTTP Content-Type header). 400 Bad Request A JSON object was expected but another JSON type was found. 400 Bad Request Invalid URL percent encoding. 400 Bad Request Invalid input: string length exceeds limit. 400 Bad Request JSON syntax error. When the error is associated with an object member, the HTTP ref member contains the name of the member. 400 Bad Request Too many levels of nesting in JSON; numbers too large to be represented; length restrictions exceeded. When the error is associated with an object member, the HTTP 18 Accessing the WSAPI

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

Table 5 Generic WSAPI
code
Member Status and Error Codes
(continued)
Description
HTTP Code
API Error Code
API Error
The server has reached its
maximum number of
connections.
503 Service
Unavailable
31
SVC_UNAVAIL
The resource is in use.
409 Conflict
34
IN_USE
The representation
specified in client's HTTP
406 Not Acceptable
35
UNSUP_REPRESENTATION
Accept
header is not
supported.
The language specified in
client's HTTP
406 Not Acceptable
36
UNSUP_LANGUAGE
Accept-Language
header is not supported.
The domain does not
exist.
404 Not Found
38
NON_EXISTENT_DOMAIN
A JSON input object
contains a name-value
400 Bad Request
39
INV_INPUT_WRONG_TYPE
pair where the type of the
value differs from what is
expected (e.g. a number
is found where a string is
expected). The HTTP
ref
member contains the
name of the name-value
pair.
A JSON input object is
missing a required
400 Bad Request
40
INV_INPUT_MISSING_REQUIRED
name-value pair. The
HTTP
ref
member
contains the expected
name.
Unsupported content (e.g.,
as specified in the HTTP
Content-Type
header).
415 Unsupported
Media Type
51
UNSUP_CONTENT
A JSON object was
expected but another
JSON type was found.
400 Bad Request
52
INV_INPUT_NOT_JSON_OBJ
Invalid URL percent
encoding.
400 Bad Request
56
INV_URL_PERCENT_ENCODING
Invalid input: string length
exceeds limit.
400 Bad Request
57
INV_INPUT_EXCEEDS_LENGTH
JSON syntax error. When
the error is associated
400 Bad Request
60
JSON_SYNTAX_ERR
with an object member,
the HTTP
ref
member
contains the name of the
member.
Too many levels of nesting
in JSON; numbers too
400 Bad Request
61
JSON_NOT_SUPPORTED
large to be represented;
length restrictions
exceeded. When the error
is associated with an
object member, the HTTP
18
Accessing the WSAPI