There's too much boilerplate for APIs right now, and many existing solutions are over-engineered for many use-cases in my opinion. I'd like to polish what I use internally, and make it available as OSS.
It could use GraphQL for the schema, but I don't use GraphQL for querying or mutations personally, queries are fine but mutations are pretty awkward, and not curl-friendly.
It would be similar to JSON-RPC, simple input and output, and the "method" in the URL, for example curl -d '{ "email": "tj@apex.sh" }' https://api.example.com/send_email. RPC has some limitations, however, in most cases I think this works great and performs perfectly fine, you can drop back to vanilla HTTP for edge-cases.
I'll add more details here if people are interested.
Features
Statically typed schema definitions, simpler than OpenAPI and friends due to RPC restrictions
Generate clients for JS, Go, TypeScript, etc
Generate documentation as markdown and HTML
Generate a server, internals of each method are user-defined
tj
commented
4 years ago
There's too much boilerplate for APIs right now, and many existing solutions are over-engineered for many use-cases in my opinion. I'd like to polish what I use internally, and make it available as OSS.
It could use GraphQL for the schema, but I don't use GraphQL for querying or mutations personally, queries are fine but mutations are pretty awkward, and not curl-friendly.
It would be similar to JSON-RPC, simple input and output, and the "method" in the URL, for example
curl -d '{ "email": "tj@apex.sh" }' https://api.example.com/send_email. RPC has some limitations, however, in most cases I think this works great and performs perfectly fine, you can drop back to vanilla HTTP for edge-cases.I'll add more details here if people are interested.
Features