Auto-generated OpenAPI spec
Auto-generated OpenAPI spec
Runtype automatically generates OpenAPI 3.0 specifications for your API surfaces, providing machine-readable documentation for API clients and code generation tools.
Accessing the OpenAPI spec
Your API Surface’s OpenAPI spec is available at:
A YAML version is also available at the same path with a .yaml extension. Find the link in the Endpoints tab of your API Surface.
What’s included
The generated spec includes:
- Endpoints — All capability endpoints with paths and methods
- Schemas — Request and response body definitions
- Authentication — Bearer token security scheme
- Error responses — Standard error formats and status codes
- Metadata — API version, Product info, contact details
Using with API clients
Import the spec into API development tools:
Postman
- Open Postman
- Click Import
- Select Link
- Paste your OpenAPI spec URL
- Click Import
Postman creates a collection with all endpoints pre-configured.
Insomnia
- Open Insomnia
- Click Create → Import from URL
- Paste your OpenAPI spec URL
- Click Fetch and Import
Bruno
- Open Bruno
- Right-click collection
- Select Import → OpenAPI
- Enter your spec URL
Code generation
Generate client libraries from the spec using OpenAPI Generator:
Supported languages include TypeScript, Python, Go, Java, Ruby, PHP, and many more.
Validating requests
Use the spec to validate requests before sending them:
Spec updates
The OpenAPI spec updates automatically when you:
- Add or remove capabilities
- Change capability configurations
- Update Product settings
Always fetch the latest spec to ensure your client code stays synchronized.
The OpenAPI spec is publicly accessible without authentication. Only actual API calls require authentication.
Spec metadata
The generated spec’s metadata section (title, description) is derived from your Product’s name and description. To update these values, edit the Product’s name or description in the Product settings.
Next steps
- Calling your API endpoints for usage examples
- Scoping API keys to capabilities
- Setting up an API Surface