postman-collection-generator

To generate a Postman collection from API routes, you scan your codebase to detect routes, HTTP methods, and parameters, producing an importable Postman Collection v2.1 JSON file. This process works by parsing code directly from frameworks like Express, Next.js, and Fastify.

Yes, you can automatically create Postman environment variables from API route definitions. The generator produces a v2.1 collection complete with environment-ready URLs and path parameters, organizing endpoints by resource for easier team collaboration.

Yes, the Postman collection generator works with Fastify, Hono, and NestJS frameworks. It scans these frameworks to discover routes and methods, detecting query and path parameters alongside request bodies to build a ready-to-share JSON file.

The best way to convert API route definitions for CI workflows is to parse the codebase and output a ready-to-share Postman Collection v2.1 JSON file. This reduces manual setup time and produces a collection suitable for automated testing workflows.

Code scanning detects request bodies and path parameters by analyzing API route definitions directly in your source code. It parses the logic of frameworks like Express and Hono, extracting HTTP methods and parameters to generate a structured Postman collection.

Postman endpoints might not be grouped by resource if the collection was built manually instead of using a code scanner. This generator organizes endpoints by resource automatically by parsing API route definitions, ensuring an organized collection structure.