Migrate from Insomnia to Cruss

Export the collections and requests you want to migrate from Insomnia using the export format supported by your current Insomnia version. Current versions export collections in the Insomnia v5 format, which Cruss does not import directly. Where your collection is available as Postman Collection v2.1 JSON, use that format; otherwise, copy the requests you need from Insomnia as cURL commands.

Create a Cruss account or sign in to an existing account so your migrated API work can live in a shared workspace and be used collaboratively by your team. Importing requires an account, so create a workspace for the API project before continuing.

Create a collection in your workspace and open its menu. Choose Import from Postman to paste a Postman Collection v2.1 file, or Import cURL to add a single request from a cURL command. cURL import brings in one request at a time, with its method, URL, headers and body, so it suits smaller sets of requests rather than a full collection migration. Review the imported requests, headers and request bodies before continuing.

Recreate the environments and variables used by your Insomnia requests in Cruss. Add the variables your API workflows depend on and verify that they resolve correctly when requests are sent.

# Insomnia environment variable
{{ _.baseUrl }}/users
{{ _.authToken }}

# Cruss: variable name only
{{baseUrl}}/users
{{authToken}}

Review authentication on the migrated requests and configure any credentials or environment variables your APIs require. Cruss supports Bearer token, Basic auth and API key authentication. If a copied cURL command included an Authorization header, it is imported as a header, so move it into the request's authentication settings or reference a variable instead. Test representative requests to confirm the migrated workflow behaves as expected.

Invite the developers who need access to the workspace and choose the appropriate role: admins manage members, editors create and edit collections and requests, and viewers have read-only access. Your team can then work from shared API collections and environments.

Once your collection is ready, open its menu and choose Generate docs to build API documentation from its requests, then publish it to get a shareable public link.

Use Cruss from the web workspace or through the VS Code extension when you want API development and testing closer to your existing development environment.

code --install-extension HyacinthOkeke.cruss