About routeman

Why it exists

Every API project ends up with a Postman collection. Someone creates it by hand on day one, it falls behind by week three, and new team members spend their first afternoon working out which request body each endpoint actually accepts.

The standard fix is to generate an OpenAPI schema and import it. That works well when the project was designed around a schema. Most Django, Flask and FastAPI codebases weren't, though. They have years of views, serializers and forms that a schema generator only partly understands, and the import still leaves you to set up login, tokens and environments.

routeman takes a different approach. It reads the application itself: the URLconf or route table the framework really serves, plus the serializers, forms, models and view code that define each request. Then it writes the collection a careful developer would write by hand, with login automated.

Principles

• Zero setup. One pip install and one command. No annotations, decorators or schema library.
• Read-only and local. routeman imports your app but never touches the database, never sends requests and never uploads anything.
• Useful on first import. Bodies that pass validation, a login request that saves the token, and environments for every server.
• No lock-in. The output is standard Postman Collection v2.1 JSON, and routeman is MIT licensed.

Who builds it

Get in touch

Bug reports, feature requests, framework edge cases and partnership enquiries are all welcome. Email routeman@swastik.ai, call +91 76545 31678, or use the contact page.