HarborClient now gives you two practical paths into other people’s API work: import an OpenCollection file from disk, or browse public collections from the apis.io catalog and pull one in with a click.

Both flows land in your local collections the same way your other imports do—so you can explore, edit, and run requests without leaving the app.

What is OpenCollection?

OpenCollection is an open, portable format for API collections. HarborClient accepts bundled OpenCollection v1.x exports as .json or .yaml files. That makes it easier to share collections across tools without locking into a single vendor export.

https://www.opencollection.com

Import an OpenCollection file

You can import from either place:

1. File → Import, or
2. Collections + → Import.

Pick your OpenCollection bundle, and HarborClient maps folders, HTTP requests, common auth (bearer, basic, and OAuth2), and pre/post scripts into a local collection. If a request uses an auth type we don’t map yet, it falls back to none—so give auth a quick check after import when something looks incomplete.

Browse public collections on apis.io

Prefer searching instead of hunting for a file? Open Add collection, switch to the Public collections tab, and search the apis.io catalog. Results focus on importable Open Collection and Postman Collection listings.

Open a result to review details, then choose Import. HarborClient downloads the artifact and runs it through the same import pipeline you already use for files—no separate storage picker, just a new collection ready to explore.

The catalog itself lives at apis.io; HarborClient is the bridge that turns a listing into a runnable collection on your machine.

Try it

Grab the latest build from harborclient.com or GitHub Releases, import an OpenCollection file—or search Public collections and pull one from apis.io.