Content-Type header
and is Accept header or by adding a
.yaml or .json extension
to the request URI. Note that it is possible for a
response to be serialized using a format different
from the request. If no response format is specified,
JSON is the default. If conflicting formats are
specified using both an Accept header and
a query extension, the query extension takes
precedence.| Format | Accept Header | Query Extension | Default |
| JSON | application/json | .json | Yes |
| YAML | application/yaml | .yaml | No |
| Code | Description |
| yyyy | Four digit year |
| MM | Two digit month |
| dd | Two digit day of month |
| T | Separator for date/time |
| HH | Two digit hour of day (00-23) |
| mm | Two digit minutes of hour |
| ss | Two digit seconds of the minute |
| Z | RFC-822 timezone |
instanceFault
examples show errors when the server has erred or
cannot perform the requested operation:code) is returned in
the body of the response for convenience. The
message element returns a
human-readable message that is appropriate for display
to the end user. The details element is
optional and may contain information that is useful
for tracking down an error, such as a stack trace. The
details element may or may not be
appropriate for display to an end user, depending on
the role and experience of the end user.instanceFault) may change depending
on the type of error. badRequest examples show errors when
the volume size is invalid:itemNotFound errors: