What it is
openapi-typescript is a monorepo of tools for consuming OpenAPI schemas in TypeScript. It lives in the TypeScript developer-tools ecosystem, sits under the Developer Tools / API Development & Testing category, ships under MIT license, and is eight years old. Repo holds 8,366 stars, 665 forks, and 300 open issues, with last push 2026-09-11T00:36:06Z. Topics tagged: openapi, openapi3, openapi3-1, swagger, typescript. Homepage at https://openapi-ts.dev.
Problem it solves: OpenAPI 3 specs — including OpenAPI 3.1 and Swagger-era schemas — describe API shapes in JSON or YAML, not in TypeScript. Handwritten types drift from spec; generated clients need types that match schema. openapi-typescript turns static OpenAPI schemas into TypeScript types, so spec stays source of truth. Second package, openapi-fetch, pairs those generated types with fetching, so calls get types derived automatically from the schema. Work happens in repo rather than per-project boilerplate.
Key capabilities
- Generate TypeScript types from static OpenAPI schemas.
- Handle OpenAPI 3 and OpenAPI 3.1 specs, plus swagger-tagged schemas.
- Ship openapi-fetch for ultra-fast fetching with types generated automatically from the OpenAPI schema.
- Split into separate packages, each with own contributing guide: openapi-typescript, openapi-fetch, docs.
- Docs site built with Vitepress, hosted on Cloudflare Pages, with Algolia-powered search.
- Funding path via OpenCollective, with gold, silver, and backer sponsor tiers.
- Public contribution flow for each package plus docs.
Who uses it and how
- Teams with OpenAPI 3 or Swagger specs generate TypeScript types instead of writing them by hand.
- Frontend and backend TypeScript projects pull generated types so request and response shapes track the schema.
- Users of openapi-fetch wire generated types into fetch calls for typed API access.
- OpenAPI 3.1 adopters rely on 3.1 support noted in repo topics.
- Docs readers use openapi-ts.dev, Vitepress-built and Cloudflare Pages-hosted, with Algolia search.
Getting started
README excerpt lists no install commands, no package manager steps, no Docker image names, and no hosted option. It points to https://openapi-ts.dev for docs, and to per-package CONTRIBUTING files in packages/openapi-typescript and packages/openapi-fetch.
When to use it — and when not to
No paid product comparison appears in the facts. README excerpt names no database, storage, or SMTP dependency, so self-hosting burden is unstated here — this is a code library and docs site, not server infrastructure. Weakness evident: 300 open issues and README excerpt carries no install or usage instructions, only docs-site link, package list,
