JsonAPI Reviews and Details

Is JsonAPI good?

Social recommendations and mentions

• GraphQL vs REST: 18 Claims Fact-Checked with Primary Sources (2026)

  REST does not define a standard batching mechanism at the protocol level. When batching is needed, it is handled through API design (such as bulk endpoints), infrastructure, or framework-specific solutions. Some specifications attempt to address this, such as OData’s batch format or JSON:API’s compound documents, but adoption is inconsistent. - Source: dev.to / 3 months ago

• Show HN: Aura – Like robots.txt, but for AI actions

  Why reinvent the wheel poorly when you have a hundred of solutions like https://jsonapi.org/? - Source: Hacker News / 12 months ago

• Build Real-Time Knowledge Graph for Documents with LLM

  For context, the subject-predicate-object pattern is known as a semantic triple or Resource Description Framework (RDF) triple: https://en.wikipedia.org/wiki/Semantic_triple They're useful for storing social network graph data, for example, and can be expressed using standards like Open Graph and JSONAPI: https://ogp.me https://jsonapi.org I've stored RDF triples in database tables and experimented with query... - Source: Hacker News / about 1 year ago

• OSF API: The Complete Guide

  Built on JSON API standards, the OSF API is intuitive for anyone familiar with REST conventions. Once you learn its core patterns, you can quickly expand into project creation, user collaboration, and more—without constantly referencing documentation. The official OSF API docs provide everything needed to get started. - Source: dev.to / about 1 year ago

• Common Mistakes in RESTful API Design

  Following established patterns reduces the learning curve for your API. Adopt conventions from JSON:API or Microsoft API Guidelines to provide consistent experiences. - Source: dev.to / over 1 year ago

• Starting the Console front-end for Rainbow Platform

  I’ve used both GraphQL and REST in the past. From json:api to Relay, each approach for building APIs has its pros and cons. However, a constant challenge is choosing between code-first and schema-first approaches. - Source: dev.to / over 1 year ago

• REST API: Best practices and design

  There is a group of people who set out to standardize JSON responses into a single response style, either for returning single or multiple resources. You can take their style as a reference when designing their API to ensure uniformity of responses. - Source: dev.to / about 2 years ago

• Path To A Clean(er) React Architecture - Domain Entities & DTOs

  The server seems to be using the popular JSON:API standard which is a great way to build APIs. But should we really use these data structures in the frontend? - Source: dev.to / about 2 years ago

• Path To A Clean(er) React Architecture - API Layer & Data Transformations

  Note: You think the response data structure with the data field and the included field with mixed data types looks weird? You might not have encountered the popular JSON:API standard yet. - Source: dev.to / about 2 years ago

• Hatchify: The Fastest Way to Build JSON: APIs

  In addition to saving you time on boilerplate, the API provided by Hatchify fully implements the JSON: API specification, which stipulates solid standards to define the peculiarities of CRUD REST APIs. Get back all the time spent bike-shedding how to implement standard API features like filtering, pagination, including related data, etc. JSON: API offers consistent practices for frontend and backend developers to... - Source: dev.to / over 2 years ago

• Show HN: Sunnybox – An Email API for Effortless IMAP Integration

  -JSON:API format responses (https://jsonapi.org) for better standardization. Built using Ruby on Rails, Sunnybox is designed to offer a powerful yet easy-to-use solution for developers managing email systems. I'd really appreciate your feedback on: - The API's user-friendliness and efficiency. - Source: Hacker News / over 2 years ago

• Custom Fields: Give Your Customers the Fields They Need

  As we’re building a RESTful API that’s formatted by the JSON:API specification and store our data in a MySQL8 relational database, a few things were pretty straightforward – we need a new model and we’ll name it Custom Field (naming wasn’t an issue here 🥲). - Source: dev.to / over 2 years ago

• How to (and how not to) design REST APIs

  I found json api spec[1] recently. This kind of is better standard for REST APIs. It is bit rough to handle client side but once you get the hang of it, it is breeze to use [1] https://jsonapi.org/. - Source: Hacker News / over 2 years ago

• Building a Secure RESTful API Using NestJS and Prisma With Minimum Code

  That's it! Now we have a complete set of RESTful CRUD APIs at "/api/zen" that conforms to the JSON:API specification, and the access policies fully protect the APIs. The API provides rich filtering and relation-fetching capabilities. The following are some examples; you can find more details here. - Source: dev.to / almost 3 years ago

• JSON Schema Store

  Does this have any relation to https://jsonapi.org/ ? - Source: Hacker News / almost 3 years ago

• An Introduction to APIs

  Basic REST and JSON RPC are very simple to start with, but have common problems when application gets bigger. How do you represent relations, pagination, filtering etc? My go-to specification for structuring JSON documents is https://jsonapi.org/ It covers most basic needs of a standard API. - Source: Hacker News / almost 3 years ago

• How to Host a RESTful API on Vercel

  Easy, isn't it? The automatically generated APIs provide resource-centric RESTful endpoints using JSON:API as the transportation format. Here're a few more advanced examples of using the API:. - Source: dev.to / about 3 years ago

• Introducing QueryR!

  Hahaha, yeah kinda. I initially built QueryR to align with the Json API spec. Source: over 3 years ago

• Step by step guide to becoming a modern back end developer in 2023

  I did for one project, although I got kicked off a year in, because they didn't know what they had. IMHO every REST API should be discoverable this way like the web, for example with links to related resources in responses (at least in dev) and by having OpenAPI documentation at a root path like / or /api. JSON API provides much of this for free when used with something like Laravel: https://jsonapi.org... - Source: Hacker News / over 3 years ago

• Show HN: Dog API

  Take a look at the JSON:API specification https://jsonapi.org. - Source: Hacker News / over 3 years ago

• are there TS community conventions for api response structure?

  Not sure it's an answer for your question. For simple api, I tend to organize something slightly based on json-api. I just add a success field to ease and open the door for discriminated unions. An example of responses would be in the lines of:. Source: almost 4 years ago