Negotiating content type
- Dean Bazeley
- James Seabrook
Most services are able to respond using a content type asked for in the Clients
Content-Type and Accept HTTP header. The following content types are supported:
Type | Mime Type | Description |
XML | application/xml | XML representation of data |
JSON | application/json | JSON representation of data |
CSV | text/csv | Comma Separated Values representation |
HTML | text/html | HTML representation primarily used for testing API calls. |
If it is not convenient to pass the desired content type using the Content-Type header, you can indicate to the hub the desired format by suffixing the URI with one of ‘xml’, ‘json’, ‘csv’ or ‘html’.
For example, to request that a service responds using XML format you could use the url:
https://hubuat1.supplystream.com/hub/api/echo/V1/hello.xml?token=<token>
or if instead you wish to receive a response as JSON, you could use
https://hubuat1.supplystream.com/hub/api/echo/V1/hello.json?token=<token>