For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Accessing the OpenAPI spec
  • What’s included
  • Using with API clients
  • Postman
  • Insomnia
  • Bruno
  • Code generation
  • Validating requests
  • Spec updates
  • Customizing the spec
  • Next steps
Products & Surfaces

Auto-generated OpenAPI spec

Was this page helpful?
Previous

Calling your API endpoints

Next
Built with

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:

https://api.runtype.com/v1/products/{productId}/surfaces/{surfaceId}/api/openapi.json

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

  1. Open Postman
  2. Click Import
  3. Select Link
  4. Paste your OpenAPI spec URL
  5. Click Import

Postman creates a collection with all endpoints pre-configured.

Insomnia

  1. Open Insomnia
  2. Click Create → Import from URL
  3. Paste your OpenAPI spec URL
  4. Click Fetch and Import

Bruno

  1. Open Bruno
  2. Right-click collection
  3. Select Import → OpenAPI
  4. Enter your spec URL

Code generation

Generate client libraries from the spec using OpenAPI Generator:

$npx @openapitools/openapi-generator-cli generate \
> -i https://api.runtype.com/v1/products/{productId}/surfaces/{surfaceId}/api/openapi.json \
> -g typescript-fetch \
> -o ./src/api-client

Supported languages include TypeScript, Python, Go, Java, Ruby, PHP, and many more.

Validating requests

Use the spec to validate requests before sending them:

1import SwaggerParser from '@apidevtools/swagger-parser';
2
3const api = await SwaggerParser.validate('https://api.runtype.com/v1/products/{productId}/surfaces/{surfaceId}/api/openapi.json');
4console.log('API name: %s, Version: %s', api.info.title, api.info.version);

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.

Customizing the spec

Add custom metadata to your spec:

  1. Go to API surface settings
  2. Click Documentation
  3. Add:
    • API description
  • Contact information
  • License details
  • External documentation links
  1. Click Save

These details appear in the generated spec’s metadata section.

Next steps

  • Calling your API endpoints for usage examples
  • Scoping API keys to capabilities
  • Setting up an API surface