Importing your spec
Upload an OpenAPI file or point to a URL. Specless handles the rest.
Upload a file
Drag your .json or .yaml file into the import area. Specless parses it immediately and shows you what it found - endpoints, schemas, auth methods.
Validation
If something looks off, you'll see validation errors inline. Fix them in your spec and re-upload. No partial imports - either the whole file passes or you get a clear error.
File size limits
Specs up to 10MB are fine. If your spec is larger than that, it probably has inline examples that could be extracted. Specless will still try, but parsing takes longer.
Link to a URL
If your spec lives at a URL (like a raw GitHub link or an API endpoint that serves the spec), paste it in. Specless fetches and parses it the same way.
Re-sync
URL imports can be set to re-sync. When your spec changes at that URL, Specless picks up the diff and regenerates your outputs.
You can set sync to manual (you trigger it), or automatic on a schedule. Automatic sync checks every hour by default.
Authentication
If your spec URL requires auth, you can add a header. Useful for private GitHub repos or internal APIs that gate their spec behind a token.
What gets parsed
Paths, methods, parameters, request/response bodies. Every operation in your spec becomes a documented endpoint and a typed SDK method.
All components/schemas definitions, including nested $ref chains. Circular refs are handled. Discriminated unions (oneOf with discriminator) map to TypeScript union types.
Security schemes - API key, Bearer token, OAuth2. Specless reads your securitySchemes and wires auth into both the SDK client and the docs.
Title, version, description, server URLs. These show up in your docs site header and in the generated package.json.
Unsupported features
Vendor extensions (x-custom-* fields) are ignored during generation. They won't break anything - they just don't affect output.
Callbacks and webhooks have limited support right now. The schemas get parsed but they don't generate SDK methods yet.
After import
Once your spec is imported, you land on the project dashboard. From there you can generate any combination of SDK, npm package, or docs.
Each output is independent. You can generate just the docs now and add the SDK later.
Last updated on