› apix

FAQ

Frequently asked questions about apix.

FAQ

Why apix over Postman?

Postman is a powerful tool, but it comes with a GUI, an Electron runtime, optional cloud sync and an account requirement. apix is the opposite: a single binary, no GUI, no internet required, no account, no telemetry.

If you live in the terminal and want to send HTTP requests without leaving it, apix is for you. If you need a visual response inspector shared across a large team, Postman might be the better fit.

Does it work on Windows?

Yes. Pre-built binaries for Windows x86_64 are available on the Releases page.

For the best experience, use apix inside a UNIX-compatible terminal:

  • WSL (Windows Subsystem for Linux) — recommended
  • Git Bash
  • Windows Terminal with PowerShell

The native Windows terminal (cmd.exe) works but some box-drawing characters may not render correctly depending on your font.

How do I update apix?

Re-run the install script — it always fetches the latest release:

bash
curl -fsSL https://raw.githubusercontent.com/CianusDev/apix/main/install.sh | bash

If you installed manually, download the latest binary from the Releases page and replace the existing one in ~/.local/bin/.

If you built from source:

bash
cd apix
git pull
cargo build --release
cp target/release/apix ~/.local/bin/

Where is my data stored?

All data is stored locally in ~/.apix/:

bash
~/.apix/
├── history.json
├── collections.json
└── environments.json

apix never sends your data anywhere. See the Data storage section for the full format reference.

How can I contribute?

Contributions are welcome! Here is the workflow:

  1. Fork the repo on GitHub
  2. Clone your fork: git clone https://github.com/<your-username>/apix.git
  3. Create a branch: git checkout -b feature/my-feature
  4. Make your changes and run the checks:
bash
cargo test    # run all tests
cargo clippy  # lint
cargo fmt     # format
  1. Commit, push and open a Pull Request against CianusDev/apix.

See the Contributing page for more details.