typeapi
typeapi copied to clipboard
apioo
TypeAPI is an OpenAPI alternative to describe REST APIs for type-safe code generation.
We need a way to describe a general API interface. I.e. we have two specifications which describe a service for sending mails. It would be great if there is a...
Some APIs use array query parameters by using a bracket `[]` notation, in this example airtable s.  At our SDK we should add support for query arrays, so that...
On some APIs there are global parameters which are applied on every API request i.e. the Notion API has a `Notion-Version` header which is required for every request s. ...
Currently TypeAPI is used to describe REST APIs for example: ```json { "operations": { "getMessage": { "description": "Returns a hello world message", "method": "GET", "path": "/hello/world", "return": { "schema": {...
Many APIs have some kind of paged collection response where the initial request only returns a subset of the complete collection i.e. ```json { "totalEntries": 1024, "itemsPerPage": 16, "startIndex": 32,...
Currently our SDK can only work with JSON payloads. We should also add support for file up/download. This means for uploads our client SDK needs to send an `multipart/form-data` request...
Hey @chriskapp -- I'm working on a very similar project to you called [Fern](https://github.com/fern-api/fern). We are also building an OpenAPI alternative that makes it easy to generate idiomatic SDKs for...
Currently a user needs to specify concrete every error code i.e. 400, 404, 500 etc. and a corresponding schema. Most APIs have a unified error response for all errors. We...
REST APIs sometime include links to other resources i.e.  it would be great if we could add some more support to resolve those links. With the client SDK you...
At a TypeAPI spec it is often the case that we describe a complete type returned by a GET operation. Most times the same type is also used to create...