Request/Response parameter formats
Some response and request parameters require an XML body. The format for such parameters is described in the following table.
The same request parameters can also be sent in JSON format.
In order to pass request parameters in JSON format, either a request parameter or
a request header with the name qpp-content-type can be passed in the request.
Following is the fallback sequence used for resolving the qpp-content-type:
-
Request Header
qpp-content-type. -
Request Parameter
qpp-content-type. -
Auto detection by Tika.
If none of the above resolves to the correct content type, the default value used is XML.
Response in JSON format already exists by specifying extra request parameter view=jsonView in the REST request.
|
Object Name |
Schema Definition |
Example |
|
|
|
XML based relations: XML Component Reference
Primary Attachment:
|
|
|
|
XML based relations: XML Component Reference
Primary Attachment:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
