Jsonapi.org Website Review

If you’ve ever argued with your team about the way your JSON responses should be formatted, JSON:API can be your anti-bikeshedding By following shared conventions, you can increase productivity, take advantage of generalized tooling, and focus on what matters: your Clients built around JSON:API are able to take advantage of its features around efficiently caching responses, sometimes eliminating Here’s an example response from a blog that implements JSON:API:     attributes: {       title: JSON:API paints my bikeshed!         data: { type: people, id: 9 }       },       lastName: Gebhardt,       twitter: dgeb         data: { type: people, id: 2 }       }     attributes: {       body: I like XML better         data: { type: people, id: 9 }       } The response above contains the first in a collection of “articles”, as well as links to subsequent members in that collection. It also contains resources linked to the article, including its author and comments. Last but not least, links are provided that can be used to fetch or update any of these resources. JSON:API covers creating and updating resources as well, not just responses. The JSON:API community has created a collection of extensions that APIs can use to provide clients with information or functionality beyond that described in the base JSON:API specification. These extensions are called profiles.