Skip to main content

Download

Download APIWeave for your desktop

APIWeave is an open-source visual API testing tool that runs on your machine. One installer, no account, no backend to stand up, and no ports left listening unless you turn the local MCP bridge on.

Open the latest release

Each release ships SHA256SUMS.txt for verifying the download.

Platforms

Pick the installer that matches your machine

The same app on all three platforms, built from the same source. Every package lands in one release page.

Windows

Windows 10 or newer (x64).

APIWeave-<version>-win-x64.zip

  1. Download the release zip and extract it.
  2. Run the installer inside. It is per-user and needs no administrator rights.
  3. Launch APIWeave from the Start menu entry it adds.

The installer and binaries are unsigned, so SmartScreen may warn on first launch: choose More info, then Run anyway.

macOS

macOS 11 (Big Sur) or newer, Intel or Apple Silicon.

APIWeave-<version>-mac-x64.dmg or -mac-arm64.dmg

  1. Open the .dmg and drag APIWeave into Applications.
  2. Right-click the app and choose Open the first time.
  3. Launch it from Applications or Spotlight after that.

The build is unsigned and un-notarized, so Gatekeeper blocks the first launch. If the right-click Open flow is not offered, clear the quarantine flag with xattr -dr com.apple.quarantine /Applications/APIWeave.app.

Linux

A current distro with glibc 2.31+ (Ubuntu 20.04+, Debian 11+, Fedora 33+).

AppImage · .deb · .rpm · .pacman

  1. Pick the package that matches your distro.
  2. Install it with your package manager, or run the AppImage directly.
  3. Launch APIWeave from the menu entry or the terminal.

The AppImage needs FUSE 2; on Arch, either install it or run the AppImage with --appimage-extract-and-run. The .pacman package has no such requirement.

Linux, by package manager

  • Debian / Ubuntu: sudo apt install ./APIWeave-<version>-linux-amd64.deb
  • Fedora / RHEL / openSUSE: sudo dnf install ./APIWeave-<version>-linux-x86_64.rpm
  • Arch / Manjaro: sudo pacman -U APIWeave-<version>-linux-x64.pacman
  • Any distro: chmod +x APIWeave-<version>-linux-x86_64.AppImage && ./APIWeave-<version>-linux-x86_64.AppImage

Run the AppImage without FUSE 2 by adding --appimage-extract-and-run. On Arch with Hyprland, the app requests native Wayland on its own; add --ozone-platform=x11 only if a compositor quirk forces XWayland.

After install

Confirm the app is healthy, then run something

There is nothing to configure before the first workflow. These are the checks that tell you the install landed properly.

Verify the install

  • The window opens on the workflows list — there is no login screen.
  • Settings → Updates shows the version you installed.
  • A data directory exists with apiweave.db and keyfile.json in it.

The data directory is the OS-standard user data path: %APPDATA%\APIWeave on Windows, ~/Library/Application Support/APIWeave on macOS, ~/.config/APIWeave on Linux. keyfile.json is the key to the encrypted secret store — treat it like a private key, because deleting it deletes the store.

Run your first workflow

  1. Build a workflow from Start, an HTTP Request node, and an Assertion node.
  2. Pick an environment in the canvas toolbar, then press Run.
  3. Watch the nodes light up, then open one for its request and response.

Updates

You decide when a new version installs

APIWeave checks GitHub Releases shortly after launch, then every six hours while the window stays open. Settings → Updates controls what happens next.

Notify me (default)

Checks happen on schedule and tell you a version exists. Nothing downloads until you ask.

Automatic

Downloads in the background and installs the next time you quit. Offered on Windows and the Linux AppImage only, the two platforms that can stage an update themselves.

Manual only

Never checks on its own. Only the Check for updates button reaches the network.

The builds are not code-signed yet, so the updater has no publisher certificate to verify a downloaded installer against. That is why Notify me is the default rather than Automatic, and why macOS and the .deb/.rpm/.pacman Linux packages only ever show a notice with a link to the release page. If an update misbehaves, Settings → Updates → Show update log opens the directory with main.log selected.