If you already have API requests in Postman, Bruno, a browser HAR capture, or an OpenAPI spec, you do not need to rebuild them by hand in HarborClient. HarborClient can import collections from several common formats — and the OpenAPI Import plugin adds support for OpenAPI 3.x documents.
This guide explains what each import path supports, how to use it, and what to expect after import.
What HarborClient can import
| Format | How to import | Typical source file |
|---|---|---|
| Postman | Built-in collection import | Postman collection export (.json) |
| Bruno | Built-in collection import | Bruno collection folder or bruno.json |
| HAR | Built-in collection import | Browser or proxy HAR capture (.har) |
| OpenAPI 3.x | OpenAPI Import plugin | OpenAPI spec (.json, .yaml, or .yml) |
Postman, Bruno, and HAR imports are built into HarborClient. OpenAPI imports require the separate OpenAPI Import plugin.
Why import collections
- Migrate from another client — bring existing Postman or Bruno work into HarborClient in one step.
- Turn browser traffic into requests — import API calls captured in a HAR file from DevTools or a proxy.
- Generate requests from a spec — create a collection from an OpenAPI document instead of typing each endpoint manually.
- Keep working locally — imports are parsed on your machine; nothing is uploaded to a cloud service.
Import Postman, Bruno, and HAR (built-in)
HarborClient detects the file type automatically when you import through the collection dialog.
- Open Add collection (for example from the sidebar or File menu).
- Select the Import from file tab.
- Click Import file and choose your export:
- Postman — a Postman collection JSON export
- Bruno — a Bruno collection folder (macOS) or
bruno.json(other platforms select the manifest file) - HAR — a
.harfile from browser DevTools or another capture tool - HarborClient — a native HarborClient collection export JSON
- Review any warnings about unsupported features or scripts, then confirm the import.
- If a collection with the same identifier already exists, choose to update it, import as a new copy, or cancel.
Postman
HarborClient reads standard Postman collection exports and converts requests, folders, variables, auth, headers, bodies, and scripts where supported.
- Supported auth includes Bearer, Basic, and OAuth2 client credentials.
- Body modes include raw (JSON/text), urlencoded, and form-data.
- Pre-request and test scripts are imported verbatim, but they may not behave exactly as they do in Postman.
- Nested Postman folders are flattened into a single folder level using names like
Parent / Child.
HarborClient shows a warning before importing Postman collections because not every Postman feature maps one-to-one. Only import collections from sources you trust.
Bruno
Bruno collections live on disk as a folder with bruno.json and request files (.bru or YAML). HarborClient walks that folder and imports HTTP requests.
- Collection-level variables, headers, auth, and scripts from
collection.bruare included when present. - Request headers, query params, bodies, auth, docs, and scripts are imported from each request file.
- Nested Bruno folders are flattened the same way as Postman folders.
- Bruno environments are not imported — only the collection itself.
On macOS you can select the Bruno collection folder directly. On other platforms, select the bruno.json file inside the collection folder.
HAR (HTTP Archive)
A HAR file records network traffic from a browser session or proxy. HarborClient converts API-like entries into saved requests.
- Imports method, URL, headers, query params, and request bodies when present.
- Skips static assets such as images, CSS, JavaScript bundles, fonts, and media.
- Focuses on API-like traffic — non-GET requests, requests with bodies, and responses that look like JSON, XML, text, or form data.
- Creates a flat collection (no folders) named from the HAR metadata or file name.
If a HAR file contains no API-like requests, the import fails with an error rather than creating an empty collection.
Import OpenAPI with the plugin
The OpenAPI Import plugin adds a dedicated workflow for OpenAPI 3.x specs. It parses the document locally, lets you preview operations, and creates a HarborClient collection grouped by OpenAPI tags.
Install the plugin
You can install the plugin from HarborClient’s plugin marketplace, or build it from source:
pnpm installpnpm build
Then in HarborClient choose Settings → Plugins → Load unpacked… and select the plugin directory. The plugin requires HarborClient 1.9.0 or later.
Import an OpenAPI spec
- Choose File → Import OpenAPI.
- Click Choose file… and select an OpenAPI 3.x
.json,.yaml, or.ymlfile. - Review the parsed operations grouped by tag. Untagged operations appear at the collection root.
- Adjust the Collection name if needed (defaults to the API title from the spec).
- Deselect any endpoints you do not want.
- Click Import collection.
For each selected operation, HarborClient creates a request with:
- Method and URL (using the first
serversURL plus the path) - Query parameters and headers from the operation definition
- JSON or text request bodies inferred from examples or simple object schemas
- Operation descriptions stored as request comments
- Folder names from the first OpenAPI tag on each operation
After import
Imported collections appear in the HarborClient sidebar like any other collection. You can edit requests, add environments, run collections, and export commands with the cURL or HTTPie plugins.
A few things are worth checking right after import:
- Auth — verify tokens, usernames, and secrets; imported values may be placeholders.
- Variables — Postman and Bruno collection variables import, but Bruno environments do not.
- Scripts — review pre/post scripts from Postman or Bruno; HarborClient uses its own
hcAPI, not Postman’spmsyntax. - Folder structure — deeply nested folders from Postman or Bruno become single-level folder names.
Limitations by format
| Format | Limitations |
|---|---|
| Postman | Unsupported auth types, GraphQL/file bodies, path variables, and saved responses may be omitted; nested folders flattened; scripts may not behave the same as Postman |
| Bruno | GraphQL, gRPC, WebSocket, file bodies, unsupported auth types, and environments omitted; nested folders flattened |
| HAR | Static assets skipped; only API-like traffic imported; no folders, variables, auth, or scripts |
| OpenAPI | OpenAPI 3.x only; limited $ref resolution; bodies inferred from JSON examples or simple object schemas only |
Import safely
Imported collections can include scripts that run inside HarborClient. Treat import files like code from an external source:
- Import only from people and projects you trust.
- Read warnings about Postman compatibility and collection scripts before confirming.
- Review imported scripts before sending requests, especially in shared or production environments.
Get started
To move existing API work into HarborClient:
- Use Add collection → Import from file for Postman, Bruno, or HAR exports.
- Install the OpenAPI Import plugin and choose File → Import OpenAPI for OpenAPI specs.
- Review auth, variables, and scripts after import, then start sending requests.
Plugin source:







Leave a Reply