Sep 30, 2022 · 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 …

Clients and servers MUST send all JSON:API payloads using the JSON:API media type in the Content-Type header. Clients and servers MUST specify the ext media type parameter in the Content-Type …

In most cases, JSON:API requires the server to return an error when it encounters an invalid value for a JSON:API–defined query parameter. However, for API-specific query parameters (i.e. those not …

In short, JSON:API is an attempt to formalize similar ad hoc client-server interfaces that use JSON as an interchange format. It is specifically focused around using those APIs with a smart client that knows …

This section contains recommendations for JSON:API implementations. These recommendations are intended to establish a level of consistency in areas that are beyond the scope of the base JSON:API …

JSON:API was originally drafted by Yehuda Katz in May 2013. This first draft was extracted from the JSON transport implicitly defined by Ember Data’s REST adapter.

Japx is lightweight JSON:API parser that flattens complex JSON:API structure and turns it into simple JSON and vice versa. It works by transferring Dictionary to Dictionary, so you can use Codable, …

The JSON:API specification provides a way to define new functionality not provided by the base specification using extensions. Additionally, it provides a means to share a particular usage of the …

Discussion forum for JSON API implementors and consumers.

Apr 2, 2025 · I’ve explored a few alternatives lately, and here are two that I think address your specific needs for REST API testing, environment management, documentation, and a lighter resource footprint: