Voyager API collections
Group related requests into a collection, and nest folders inside it, instead of scrolling through every request you've ever made in one flat list.
What it does
The sidebar lists your collections, each expandable into its folders and requests. New collections, folders, and requests are created from the sidebar directly, with rename and delete available on each node. A request doesn't have to belong to a collection to exist — it can stay "unfiled" as a scratch request, then get filed into a collection later via a save dialog with a collection picker.
Collections also carry their own environment and auth context that requests inside them can use, and collections built elsewhere aren't a dead end — Postman, Insomnia, Thunder Client, and OpenAPI/Swagger collections can be imported directly.
Use cases
- Keeping one collection per service or per project instead of one long request list.
- Mirroring an API's own resource structure with nested folders.
- Bringing an existing Postman workspace into Voyager without re-creating every request by hand.
Frequently asked questions
Can I nest folders inside a collection?
Yes, folders can be nested inside a collection to mirror how you think about the API you’re working with.
What happens to a request I haven’t filed into a collection yet?
It stays in an "Unfiled" scratch area — you can send and iterate on it without deciding on a collection first, then save it into a collection later.
Can I import an existing Postman or Insomnia collection?
Yes, both are supported importers, along with Thunder Client and OpenAPI/Swagger documents.
Related: Environments · Postman alternative