Specless

What you get

A docs site with every endpoint, schema, and auth method from your spec. Request and response examples are generated from your schemas. No manual writing needed.

Endpoint pages

Each endpoint page shows:

Method and path
Parameters (path, query, header)
Request body with schema
Response codes and bodies
Auth requirements

Try it out

Each endpoint has a "Try it" panel. Fill in parameters, set auth, hit send. The request goes to your actual API server. Useful for testing and for showing consumers how the API works.

Code examples

Every endpoint gets copy-paste code snippets in multiple languages - TypeScript, Python, cURL. Generated from the actual request shape, not generic templates.

Schemas

All your components/schemas are documented on their own pages. Properties, types, required fields, enums, nested objects - everything rendered from the spec.

Schema pages link back to the endpoints that use them, so consumers can jump between "what does this object look like" and "where do I send it."

Search

Full-text search across all endpoints, schemas, and descriptions. Works client-side, no backend needed.

Every docs site gets a URL. Share it with your team, your API consumers, or make it public.

Direct links

Every page has a stable URL based on the operation ID or path. Link to a specific endpoint in your Slack, README, or support docs.

Embedding

You can embed the docs in your own site using an iframe. The embed strips navigation chrome so it fits inside your existing layout.

Keeping docs updated

If you imported your spec from a URL with re-sync enabled, docs update automatically when your spec changes. No action needed.

Re-upload the updated spec. Specless diffs the changes and updates only what changed. Your URL stays the same.

Customization

Branding

Set your logo, colors, and favicon. The docs site picks up your brand so it doesn't look like a generic tool output.

Custom domain

Point your own subdomain at the docs. Add a CNAME record, verify it in Specless, done. SSL is automatic.

Visibility

Private docs require auth to view - useful for internal APIs or partner integrations where you control who sees what.

Set docs to public or private. Toggle anytime from the project dashboard.

The content comes from your spec. Write good description fields in your OpenAPI file and they show up here. Specless doesn't add or remove anything. If a description is missing, the field shows up blank.

API docs