Questions about how Cruss compares? Here are some common questions about API development, collaboration and migration.
What is the main difference between Postman and Cruss?
Postman is a widely used API development and testing platform. Cruss is built around a shared workspace where teams can build, test, document and share API workflows together.
Can I import my Postman collections into Cruss?
Yes. Cruss supports Postman Collection v2.1 import. Export the collection from Postman and import the JSON into Cruss, then review the imported requests and configuration. Request names, methods, URLs, headers and bodies are imported; authentication and folder structure need to be set up again. The Postman migration guide covers the full workflow.
Does Cruss support collection-based API testing?
Yes. The Collection Runner runs every request in a collection, including sub-folders, as a repeatable sequence and can pass values from one response into later requests. Individual requests can also carry assertions on status code, response time, body content, JSON fields and headers, which are checked each time the request is sent.
Can Cruss work with local APIs?
Yes. Run npx cruss-agent to let the Cruss web app send requests to APIs running on localhost, or use the Cruss VS Code extension to send requests from your editor. Either way you can test APIs running in your development environment.
Does Cruss support API documentation?
Yes. API documentation is part of the Cruss workspace, allowing teams to document and share their APIs alongside the collections and workflows used to develop them. Documentation is generated from a collection and can be published as a shareable page.