...
Most services respond to the HTTP HTTPS method GET while certain others respond to both GET and POST. The applicable methods per service are described under each service group. Either protocol HTTP or HTTPs is acceptable.
Responses
The response serialization for each service is dictated by the HTTP header HTTPS header Accept. The following table lists the possible return formats. Each format will be is described in the response section of the respective service method. Not all formats are applicable to all requests.
Accept | Serialization |
|---|---|
application/json | JSON |
text/xml | XML |
text/html | XHTML currently unused but may be supported in the future |
CDWS determines the serialization method of the output in the following order:
- HTTP HTTPS header:
Accept - Query parameter:
content-type - Pre-defined default per service (JSON with the exception of
/textwhich defaults to XML)
Typically, clients will have their own method of setting request HTTP HTTPS headers.
The following examples use the UNIX wget command line utility.
...
| Code Block |
|---|
wget -O- \ --header 'x-user: x' \ --header 'x-password: y' \ --header="Accept:text/xml" 'httphttps://cdws21.ificlaims.com/search/query?q=pn:ep-0700000-b1' |
...
Example 2: setting the content-type as a query-string parameter
...
wget -O- \ |
...
|
...
|
...
|
...
https://cdws21.ificlaims.com/search/query?q=solr&content-type=text/xml' |
Note: All CDWS responses can be returned as either JSON or XML. The only exception is the attachment service method /attachment/fetch which returns the image bytes with corresponding response headers last-modified, content-type, and content-length appropriately populated.
Although the serialization is predetermined by the request content-type, the response format for for each service group differs. The response formats will be are described under their respective service groups:
| Children Display | ||
|---|---|---|
|