api-guidelines
json-api
Our great sponsors
api-guidelines | json-api | |
---|---|---|
15 | 59 | |
22,391 | 7,314 | |
0.4% | 0.5% | |
8.8 | 4.9 | |
3 days ago | 7 days ago | |
CSS | ||
GNU General Public License v3.0 or later | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
api-guidelines
-
Mastering API Design: 26 Resources for Software Engineers
đź“ť "Microsoft REST API Guidelines" [link]
- Ask HN: Any book recommendations for API design?
- What are the best practices that you, your team or your company follows while developing apis or while writing api contracts?
- Recommendations for resources about REST APIs?
- Best Practice/Standars for API Management endpoints
- Ask HN: Standards for API Error Responses
-
Recommendation reading (books/blogs) for best practices while designing REST APIs
This is a great, thorough and in-depth document from Microsoft: https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md
-
Looking for understandable good practices concerning structure of json returned
Thing is, I made some researches this morning, and I found nowhere a "data" wrapper, not in Microsoft API best practices [FR] (client is using Microsoft APIs), not in Microsoft API guidelines, not in OpenAPI offical specifications, nowhere in any blog I found this morning.
-
Everything about APIs
Microsoft REST API guidelines
-
Library for Filtering/Sorting/Pagination Microsoft Style
I'm working on a web API where I'd like to follow the Microsoft API Guidelines. I thought this would be easy, because surely there would be plenty of libraries out there to support their guidelines, maybe Microsoft even has one out there (I thought). I haven't been able to find any.
json-api
-
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 agree on how resources are fetched and returned. Since Hatchify provides the core of your API for you, you can count on it’s standardized functionality to give your API a consistent start.
- SQL as API
-
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.
-
What if an SQL Statement Returned a Database?
https://github.com/json-api/json-api/issues/795
There is an atomic operations extension:
-
A View on Functional Software Architecture
JSON:API to format each message
-
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 🥲).
-
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/
-
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.
-
JSON Schema Store
Does this have any relation to https://jsonapi.org/ ?
-
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.
What are some alternatives?
google.aip.dev - API Improvement Proposals. https://aip.dev/
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
apollo - 🚀 Apollo/GraphQL integration for VueJS
free-for-dev - A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
laravel-json-api - JSON API (jsonapi.org) package for Laravel applications.
OpenAPI-Specification - The OpenAPI Specification Repository
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
awesome-rest - A collaborative list of great resources about RESTful API architecture, development, test, and performance
grpc-swift - The Swift language implementation of gRPC.
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
zenstack - Typescript toolkit on top of Prisma ORM, offering flexible and declarative Access Control Policy(Authorization/Permission) for RBAC/ABAC/PBAC/ReBAC with auto-generated type-safe APIs and frontend hooks.