Summary
An API you have no client for.
Between the Swagger document and a generic request call, an internal service becomes usable in a session without anyone writing an integration first: find the endpoint, read what it takes, call it.
What it is
A general REST client. You configure it once with a base URL and credentials, optionally give it a Swagger or OpenAPI URL, and then call GET, POST, PUT, DELETE and PATCH against that API. Token refresh and retries are handled inside.
What you get
- One API configured with its base URL, a timeout and a retry count
- Either a bearer token, or a username and password posted to a login endpoint, with re-authentication handled for you
- Any HTTP method called against a path, with query parameters, a body and extra headers
- The endpoint list read out of the API's Swagger or OpenAPI document
- Endpoints searched by keyword, and one read in detail before you call it
Requirements
Node to build and run it, plus whatever the API you point it at needs — a token, or a username and password with the login path and the field the token comes back in.