Supported Media Types
Media types let you choose the format of the data you want to receive, defining the structure of the HTTP payloads exchanged between the server and the client. They allow a REST API to inform the client how to interpret the data in the payload.
Note:
Use theAccept
HTTP header
in the client to specify the media types for the response from the
server. You can specify:
application/json
in the request accept header when a superset of all supported media types may be accepted in the response.application/vnd.oracle.adf.resourceitem+json;q=0
in the request accept header when you want to get only the response code and not the response body.
The following table lists
the supported media types for the Content-Type
header.
Media Type | Description |
---|---|
application/vnd.oracle.adf.resourcecollection+json |
Represents a resource collection. |
application/vnd.oracle.adf.resourceitem+json |
Represents a resource item. |
application/vnd.oracle.adf.action+json |
Describes a custom action execution and its parameters. |
application/vnd.oracle.adf.actionresult+json
|
Describes the result of an action execution. |
application/vnd.oracle.adf.description+json |
Describes a single resource, a resource hierarchy, or an entire catalog. |
application/vnd.oracle.adf.batch+json
|
Represents multiple requests grouped together and the client provides identification for each part in the batch request. |
application/vnd.oracle.adf.swagger+json |
Represents the runtime swagger returned by the server. |
application/json |
Represents content in JSON format. This media type is supported by SCIM and BPM resources. |