Summary
Finding a public API's definition and putting it into your specs folder is one session's work.
The two halves are built to meet: the directory answers which providers, services and versions exist and where their definitions live, and the download tool writes one into the local folder under a name you pick. Editing is whole-file — a spec is read entirely and written entirely — which suits documents that are regenerated as often as they are hand-edited. The directory metrics are the cheapest way to see the scale of what is on offer before browsing it.
What it is
A manager for a local folder of OpenAPI specification files, with the APIs.guru directory attached for finding more.
What you get
- The specification files in the folder listed, one read, one written, and one downloaded from a URL straight into the folder under a filename you choose.
- The APIs.guru directory browsed: every API with links to its OpenAPI definition, the providers, one provider's APIs and service names, and a specific API version with or without a service name.
- The directory's own metrics, covering how many APIs and endpoints it holds.
Requirements
A specs folder on disk for the specification files to live in.
Setup effort
One command — npm install -g specbridge