openapi-directory
openapi-generator
openapi-directory | openapi-generator | |
---|---|---|
11 | 234 | |
3,664 | 19,899 | |
1.0% | 1.9% | |
9.2 | 9.9 | |
1 day ago | 1 day ago | |
Java | ||
Creative Commons Zero v1.0 Universal | 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.
openapi-directory
-
What is API Discovery, and How to Use it to Reduce Your Attack Surface
Use APIs.gurufor exploring well-documented OpenAPI files. For example, imagine you are interested in integrating a weather API. By searching for "weather" on APIs.guru, you find several options.
-
How to Automatically Consume RESTful APIs in Your Frontend
Furthermore, since we can split the generated code into multiple parts based on tag filtering, we can also create different SDKs from different resources or even publicly available APIs. There is an extensive list of publicly available OpenAPI specifications on SwaggerHub, RapidAPI and APIs.guru.
-
ApiVault: One-Stop Resource for API Integration
Maybe you'd like to integrate with APIs.guru?
https://apis.guru
- Show HN: An open-source OpenAPI package manager – openpm.ai
-
Automatic npm publishing, with GitHub Actions & npm granular tokens
In this specific case, I'm auto-publishing (now fully automatically, once a month) a package that wraps content from elsewhere bundling it with some utilities to make that useful in JS and available via NPM. For cases like this it's useful to have a patch update once a month that just updates the upstream content & republishes.
-
APIRank.dev - we crawled and ranked 5651+ public APIs from the internet 🔭
- Crawl API repositories like apis.guru
-
Making a useful REST API Specification
This should go without saying, but the types inside your API specification should be specific in order to be useful. The main way I see this appear is that some specification generators seem to default to "string" for everything, even if something else makes sense. In an analysis of 1154 specifications from OpenAPI directory, I found that 60% of the field types were strings. Many of these were instances that made sense, such as IDs or names, but many were misused types: for example, there was a year value encoded with type "string," and a boolean value with type "string" and enum "true" or "false". Using too-broad types such as strings can make it harder to understand the specification, and decrease the effectiveness of certain tools.
-
Data noob here - I’m looking to create my first ‘data’ project.. I want to create a basic data pipeline via an API with Python into SQL then to Power BI.. what are some well known live data sources that I should practice with?
I haven’t used it but have skimmed through it, but https://apis.guru has collected information on lots of APIs. You might find something interesting.
-
From OpenAPI to a working integration in minutes
Try the integration designer with your OpenAPI documents. If you don’t have any document handy, we prepared a few examples for you, or you can find more OpenAPI documents on APIs.guru.
-
What in your opinion is a growing trend? What should people and organisations be paying attention to going forward?
apis.guru is a nice site with APIs listed for many orgs.
openapi-generator
-
The Stainless SDK Generator
Disclaimer: We're an early adopter of Stainless at Mux.
I've spent more of my time than I'd like to admit managing both OpenAPi spec files [1] and fighting with openapi-generator [2] than any sane person should have to. While it's great having the freedom to change the templates an thus generated SDKs you get with using that sort of approach, it's also super time consuming, and when you have a lot of SDKs (we have 6 generated SDKs), in my experience it needs someone devoted to managing the process, staying up with template changes etc.
Excited to see more SDK languages come to Stainless!
[1] https://www.mux.com/blog/an-adventure-in-openapi-v3-api-code...
[2] https://github.com/OpenAPITools/openapi-generator
-
FastAPI Got Me an OpenAPI Spec Really... Fast
As a result, the following specification can be used to generate clients in a number of different languages via OpenAPI Generator.
-
Show HN: Manage on-prem servers from my smartphone
Of course you can compile the server from source if you have Go and the OpenAPI generator JAR (https://github.com/OpenAPITools/openapi-generator?tab=readme...)
Follow these steps : https://github.com/c100k/rebootx-on-prem/blob/master/.github...
And then :
(cd ./impl/http-server-go && GOARCH=amd64 GOOS=openbsd go build -o /app/rebootx-on-prem-http-server-go-openbsd-amd64 -v)
By adapting the arch if needed. Not tested, but it should work.
- OpenAPI Generator v7.3.0 has new generators for Rust, Kotlin, Scala and Java
-
Stop creating HTTP clients manually - Part I
TL;DR: Start generating your HTTP clients and all the DTOs of the requests and responses automatically from your API, using openapi-generator instead of writing your own.
-
How to Automatically Consume RESTful APIs in Your Frontend
As an alternative, you can also use the official OpenAPI Generator, which is a more generic tool supporting a wide range of languages and frameworks.
-
Building a world-class suite of SDKs is easy with Speakeasy
I trialed generating SDKs using the OpenAPI Generator package, which was largely unsatisfactory.
-
Best way to implement base class for API calls?
If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.
-
Sharing EF data access project DLL vs NuGet vs ?
For a run of the mill REST API you should generate OpenAPI (Swagger) info for the API using a library like NSwag or Swashbuckle. You'd want to do this no matter what because it's documentation for the API, but the bonus is that you can use it with tools like OpenAPI Generator to create API client code and models in a variety of languages. You certainly can create an API client library manually, it would entail having a nuget package with a class library that contains the models and client code for calling the endpoints (which I'd create using a lib such as RestEase unless you just enjoy writing boilerplate code by hand). However 95% of the time it simply isn't worth creating your own lib when OpenAPI is available because once you've done it a time or two it takes less than 5 min to run the generator and create (or update) a lib.
-
Created an API using Gin, want to create sdk for him
Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.
What are some alternatives?
postman-contract-test-generator - Postman collection and environment that will take an Open API Spec, validate component adherence, generate contract tests, and execute them.
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
atoz - Amazon Web Services (AWS) APIs in Nim
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
SpaceX-API - :rocket: Open Source REST API for SpaceX launch, rocket, core, capsule, starlink, launchpad, and landing pad data.
SvelteKit - web development, streamlined
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
smithy - Smithy is a protocol-agnostic interface definition language and set of tools for generating clients, servers, and documentation for any programming language.
awesomekql - Microsoft Sentinel, Defender for Endpoint - KQL Detection Packs
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
openapi-directory-js - Building & bundling https://github.com/APIs-guru/openapi-directory for easy use from JS
autorest - OpenAPI (f.k.a Swagger) Specification code generator. Supports C#, PowerShell, Go, Java, Node.js, TypeScript, Python