Need an OpenAPI spec and don’t have one? Your framework can probably generate it. Where the spec lives in FastAPI, NestJS, Express, Laravel, ASP.NET Core, Django and Spring Boot, how to export it as a file, and what to fix before a tool builds on it.
Launch your n8n integration - NativeShip.io
In this video:
- Code-first vs hand-written specs, and why hand-written ones drift
- FastAPI: /openapi.json, and fixing the long default operationIds
- NestJS: @nestjs/swagger, operationIdFactory, and the CLI plugin for DTO fields
- Express: zod-to-openapi, tsoa, or swagger-jsdoc
- Laravel (Scramble), ASP.NET Core (AddOpenApi), Django (drf-spectacular), Spring Boot (springdoc)
- Postman collections and Swagger 2.0 files: converting to OpenAPI 3
- Export, lint and commit the spec, then check it the way a tool reads it
Chapters
0:00 “Paste your OpenAPI spec”
0:44 Your code already knows
1:20 FastAPI: it’s already at /openapi.json
2:10 NestJS: one module, and decorators
3:00 Express: pick where the truth lives
3:38 Laravel, ASP.NET, Django, Spring
4:34 Postman collection, or an old Swagger file
5:10 Make it a file, and check it
6:17 Recap
Written version, with every command: [GUIDE URL]
Make the spec good, not only present: https://youtu.be/vPVIMnVclqA
Build an n8n node from it by hand, a 10-part series: https://www.youtube.com/playlist?list=PLYkThRYZ5f5g