Create a command line interface from a REST API.

It seems powerful!

Joat uses a YAML file to define subcommands of two types: requests and scripts. Requests subcommands ease the interaction with a REST API and scripts combine multiple commands into a more convenient one.

When designing a hypermedia API, you're really designing for a client that does not, and will never, exist. Imagine you're asked by your manager to create a "REST API" for your business.

Convert a Postgres SQL database directly into an HTTP API

<div>
    <div>
      Name: Joe Blow
    </div>
    <div>
      Email: joe@blow.com
    </div>
    <div>
      <a href="/contacts/42/edit">Edit</a>
      <a href="/contacts/42/email">Email</a>
      <a href="/contacts/42/archive">Archive</a>
    </div>
  </div>

→

So, what makes this HTML/hypertext special? The answer is also simple: this bit of HTML encodes both the data about the contact as well as the actions available on that data, in the form of hyperlinks.

Formalizing REST APIs

My API is up to level 2 on the Richardson Maturity Model. So my API is more an HTTP+JSON RPC than Rest.

The short answer to this question is that HATEOAS isn’t a good fit for most modern use cases for APIs. That is why after almost 20 years, HATEOAS still hasn’t gained wide adoption among developers. GraphQL on the other hand is spreading like wildfire because it solves real-world problems. ‒ GraphQL and REST Level 3 (HATEOAS)

I feel this feeling too that something is wrong

Develop an API that is fast :)
Everything is built in: Swagger or OpenAPI, including the tests.

Here a quickstart