Why Choose API Builder?
Teams choose API Builder because their developers stop writing client SDKs — and their APIs get better. Whether it's your only API tool or a complement to your existing stack, API Builder earns its place through generated code quality, comprehensive validation, and a workflow that gets out of your way.
✦ Quality
- High quality generated clients — Teams that adopt API Builder stop writing client SDKs entirely. The generated clients are high enough quality that developers actually prefer them — freeing up time for product work.
- Comprehensive validation — Every upload runs extensive checks to ensure internal consistency — all types, names, and references are validated. This catches problems at definition time, before they reach generated code.
- Testability of clients — Generated mock clients share the same interface definition, so teams can rely on mocks for automated tests and override only what's needed for each scenario.
⚡ Flexibility
- Resource centric — Define resources first, then expose operations on them. This aligns with modern resource-oriented tooling like GraphQL, where high quality metadata on available resources is essential.
- First class union types — Union types — a type constrained to one of a known set — are first class in API Builder. Create new types instead of continually adding optional fields to existing ones.
- Multiple input formats — Author specs in api.json, Swagger, Avro, or other IDLs. Adding new input formats is straightforward.
- Easy to add code generators — Generators are REST services that accept a service description and return a string. Teams write their own — even small, disposable ones — to solve problems in an automated fashion.
⚙ Workflow
- Integrated tooling — The entire hosted platform runs on the API Builder API, so it's simple to automate workflows. Teams write linters that enforce naming standards as part of CI. The CLI is complete enough that many teams skip the UI entirely.
- Discovery — Free hosting at app.apibuilder.io for both private and public projects makes service discovery easy across your organization.
- Versioning — Every change to every API is recorded with a list of safe and potentially breaking changes. Teams use these for release notes — for example, the API Builder API's own history.
◈ Simplicity
- Simple input format — The default api.json format is JSON that's approachable by a novice. No $ref, no oneOf — just look at an existing example and modify it for your application.
- Clean service specification — API Builder separates input format from service description. Regardless of how you author your spec, the output is a fully expanded, complete service description — easy to parse and use directly.
Ready to try it?
Get Started