Media Types
The Akana OAuth API uses the media types listed below, in either the request or response messages or both.
| Mediatype | in Req? | In Resp? | Description |
|---|---|---|---|
| application/json | Yes | Yes | JSON format. |
| application/vnd.soa.v71+json | Yes | Yes | A custom media type that can be used with version 7.1 of the product: essentially, a JSON format. |
| application/vnd.soa.v72+json | Yes | Yes | A custom media type that can be used with version 7.2 of the product: essentially, a JSON format. |
| application/xml | Yes | Yes | XML format. |
| application/vnd.soa.v71+xml | Yes | Yes | A custom media type that can be used with version 7.1 of the product: essentially, an XML format. |
| application/vnd.soa.v72+xml | Yes | Yes | A custom media type that can be used with version 7.2 of the product: essentially, an XML format. |
| application/x-www-form-urlencoded | Yes | No | The message information is URL-encoded. |
| */* | Yes | No | Used in a request to indicate that the expected response can be any format. |
| multipart/form-data | Yes |
A format used when the content has multiple sections of different content types. The multipart/form-data media type has separate components, separated by boundaries, and each component has its own media type. |
|
| text/markdown | No | No |
Indicates that the content is some type of markup; that is, essentially plain text with some formatting instruction syntax included, such as bold, italics, or heading style, to determine how the content is displayed. Used in association with certain board items, such as discussions or tickets, to identify whether the board item is in plain text or uses markup to add formatting. |
| text/plain | Yes | Plain text. | |
| text/xml | Yes | Yes | XML format. |
