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 / about 1 month ago
-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 / 4 months ago
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 / 5 months ago
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 / 6 months ago
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 / 8 months ago
Does this have any relation to https://jsonapi.org/ ? - Source: Hacker News / 8 months ago
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 / 9 months ago
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 / 11 months ago
Hahaha, yeah kinda. I initially built QueryR to align with the Json API spec. Source: over 1 year ago
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 1 year ago
Take a look at the JSON:API specification https://jsonapi.org. - Source: Hacker News / over 1 year ago
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: over 1 year ago
I noticed you make a JSON API (notice there's JSON:API specification a misnomer. That was an attempt before OpenAPI came. That was popular with Ember.). Source: over 1 year ago
Why reinvent the wheel? Just use a common standard... I prefer https://jsonapi.org/. - Source: Hacker News / over 1 year ago
It's worth noting, REST itself is just a method of data transport, and while it has some general guidelines of how that data should be represented, every API is going to be slightly different. The data in REST API's can be structured in many ways , such as json:api or Open API, but every company and developer is going to have their own preference, and the majority of API's you work with won't follow any specific... Source: almost 2 years ago
With async false, you'll want to pre-load the data - like if you're using http://jsonapi.org/ for your backend (basically GraphQL, but relying on REST / existing technologies). Source: almost 2 years ago
My guess is you would have to make sure your api is returning data in a specific standard like https://jsonapi.org/, then find react tools that can bind to the error objects. Source: about 2 years ago
Why do norms based on polymorphism exists then, like https://jsonapi.org/ , I wonder :). Source: about 2 years ago
I'm trying to create an SDK to connect for an API done with jsonapi (https://jsonapi.org/) , however I'm having problems trying to do POST request. Source: about 2 years ago
There's a million different approaches but might I suggest json:api, which is all about the structure of your requests and responses, but makes no demands on your URL structure, for instance. It is intended as an anti-bikeshedding tool. Source: over 2 years ago
Orbit.js does some of these things and coordinates client with a variety of data sources through a standard set of interfaces and using normalized data structures. I believe Orbit.js was inspired by Ember Data, as I know Dan Gebhardt is involved with Ember.js and https://jsonapi.org. - Source: Hacker News / over 2 years ago
Do you know an article comparing JsonAPI to other products?
Suggest a link to a post with product alternatives.
This is an informative page about JsonAPI. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.