api-guidelines
webmachine
Our great sponsors
| api-guidelines | webmachine | |
|---|---|---|
| 15 | 2 | |
| 22,391 | 1,498 | |
| 0.4% | -0.1% | |
| 8.8 | 2.9 | |
| 3 days ago | 2 months ago | |
| Erlang | ||
| GNU General Public License v3.0 or later | Apache License 2.0 |
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.
webmachine
- Work in progress on a port of Webmachine
-
Best Practices for REST API Design
I interrupted my reading at 'Accept and respond with JSON' to write this comment, before I skipped over that section and returned to reading the rest.
Folks that aren't aware of Webmachine should take a look:
https://github.com/webmachine/webmachine
The 'Accept' header should determine the response type, but content negotiation is something that few bother to implement. Webmachine does that for you.
Also, shameless plug for my OCaml port:
https://github.com/inhabitedtype/ocaml-webmachine
What are some alternatives?
google.aip.dev - API Improvement Proposals. https://aip.dev/
OpenAPI-Specification - The OpenAPI Specification Repository
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
free-for-dev - A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
swagger-tools - A Node.js and browser module that provides tooling around Swagger.
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
awesome-rest - A collaborative list of great resources about RESTful API architecture, development, test, and performance
http-decision-diagram - An activity diagram to describe the resolution of HTTP response status codes, given various headers.
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
cl-webmachine - HTTP Semantic Awareness on top of Hunchentoot