Skip to content

Clarify combination of JSON:API with other standars #1772

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Nov 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions _format/1.2/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,14 @@ JSON:API requires use of the JSON:API media type
([`application/vnd.api+json`](http://www.iana.org/assignments/media-types/application/vnd.api+json))
for exchanging data.

> For additional needs of HTTP APIs, like authentication, documentation, file
> uploads, and more, JSON:API can and should be combined with additional
> standards such as [OAuth 2.0](https://datatracker.ietf.org/doc/html/rfc6749)
> for authorization and [Open API](https://spec.openapis.org/oas/latest.html)
> for documentation. It is allowed for a server supporting JSON:API to also
> support other API standards on the same or other endpoints, such as
> [OData](https://www.odata.org/) or [GraphQL](https://graphql.org/).

## <a href="#semantics" id="semantics" class="headerlink"></a> Semantics

All document members, query parameters, and processing rules defined by
Expand Down
Loading
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy