This document covers information about the content type used by the wunderbon API



This is what says: "If youโ€™ve ever argued with your team about the way your JSON responses should be formatted, JSON:API can be your anti-bikeshedding tool.

By following shared conventions, you can increase productivity, take advantage of generalized tooling, and focus on what matters: your application."

wunderbon provides all data following exactly one standard. The standard we have chosen to be the one for us is called JSON:API. Here you will find information and some links for a deeper understanding.

The wunderbon API only accept the content type(s) listed below. By default, we return always content type application/vnd.api+json but this may change in the future. If you do not request a specific version of the wunderbon API (which will result in calling always the latest version), then you probably will go into a risk of a false media type returned. So our advice is to request application/vnd.api+json with every single request.


Content-Type, Media-Type or MIME-Type

The Content-Type is known under different names evolved over the past years. So the Content-Type described here is the one we use when delivering data. So it is the one you will send in a clients request.


Supported Content-Types

For more information about this Content-Type see our documentation or this reference.

Accept Header

With the Accept header you can address the Content-Type you want to receive from the wunderbon API. Please keep in mind, that we can only return the Content-Type listed under Supported Content-Types.

Accept: application/vnd.api+json

With this header you can explicitly request the Content-Type from the wunderbon API.

Whatโ€™s Next

Continue with our guided tour. Now, we would like to tell you more about how Filters help you to retrieve the right data from the wunderbon API ...