ORM Studio

Export Collections

Download Postman, Insomnia, and OpenAPI collections from your discovered routes.

3 min readDocumentationEdit this page

Export Collections

The Collections panel generates and downloads API collections from your discovered routes. Import them into Postman, Insomnia, or any OpenAPI-compatible tool with a single click.

Opening Collections

Click Collections in the sidebar.

Available Formats

Postman Collection v2.1

Downloads a postman-collection.json file compatible with Postman Collection format v2.1.

Includes:

  • All discovered routes as requests
  • Routes grouped by first path segment (folder per prefix)
  • Pre-configured Content-Type: application/json header
  • Disabled Authorization: Bearer {{token}} header (enable and fill in as needed)
  • Path variables for :param segments
  • Sample JSON body for POST, PUT, PATCH routes
  • Collection-level variables: baseUrl and token

Import into Postman:

  1. Open Postman
  2. Click Import
  3. Drop the downloaded file or click Upload Files
  4. Click Import

Insomnia Collection

Downloads an insomnia-collection.json file in Insomnia Export v4 format.

Includes:

  • A workspace named after your app
  • A Development environment with baseUrl and token variables
  • All routes as individual requests
  • Bearer token authentication (disabled by default)

Import into Insomnia:

  1. Open Insomnia
  2. Click Preferences → Data → Import Data
  3. Select the downloaded file

OpenAPI 3.0.3 Specification

Downloads an openapi.json file compliant with the OpenAPI 3.0.3 specification.

Includes:

  • info with app name and version
  • servers with your app URL
  • All routes as paths with correct HTTP methods
  • Path parameters from :param segments
  • Request body schema for POST, PUT, PATCH routes
  • Standard response codes (200, 400, 401, 404, 500)
  • bearerAuth security scheme for routes with authenticate middleware

Compatible with:

  • Swagger UI
  • Redoc
  • Stoplight Studio
  • Any OpenAPI code generator

Endpoints Preview

Below the export cards, a table previews all endpoints that will be included in the exported collection:

MethodPathHandler
GET/healthanonymous
GET/usersthis.list
POST/usersthis.create
GET/users/:idthis.getById

Re-exporting After Changes

Collections are generated from the current state of your routes at the moment you click Download. After adding or removing routes, click Refresh in the top bar and then re-download the collection.

Example Postman Collection Structure

json
{
  "info": {
    "name": "my-api API",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    {
      "name": "/users",
      "item": [
        {
          "name": "GET /users",
          "request": {
            "method": "GET",
            "url": "http://localhost:3000/users"
          }
        },
        {
          "name": "POST /users",
          "request": {
            "method": "POST",
            "header": [{ "key": "Content-Type", "value": "application/json" }],
            "body": { "mode": "raw", "raw": "{\"name\":\"John Doe\",\"email\":\"john@example.com\"}" }
          }
        }
      ]
    }
  ],
  "variable": [
    { "key": "baseUrl", "value": "http://localhost:3000" },
    { "key": "token",   "value": "" }
  ]
}

Help improve the documentation

AxilJS is open source and documentation improvements are welcome.

AxilJS DocumentationMIT License · Built by SyntaxilitY