Initialize
Scaffold .apifire/, auth.yaml, config.yaml, requests/example.yaml, and .env.example from one command.
CLI API TESTING / FILE-FIRST WORKFLOW
CLI API testing built for file-first teams.
apifire is a command-line API testing tool for developers who want real request flows, auth, validation, and repeatable checks without living in a GUI.
- Core commands and request flows, all in one workflow
- Init / auth / validate / run workflow
- Built for teams that prefer files over clicks
$apifire --version
apifire 0.1.0
$apifire init -n demo -u https://api.example.com
✓ Project initialized successfully!
Creates .apifire/, .env.example, and example request YAML.
$apifire run --parallel
Running request suite from .apifire/requests/*
$apifire auth --token-only
Designed for shell scripts and CI glue.
Explore the product
Start here, then move into the reference pages.
Route
Download
Install apifire, starting with macOS Homebrew Cask, then continue into the first-run workflow.
Route
Quick Start
Go from installed CLI to init, configure, and first run with the core setup flow.
Route
Docs
Read the core usage guide for install, init, auth, request schema, validation, variables, and CI workflows.
Route
Commands
Scan the small command surface, jump to a subcommand, and copy known-good examples quickly.
Route
Examples
Review the scaffolded YAML files that turn tests into versioned project assets.
Route
Skills
Learn how the apifire Claude Code skill turns natural-language requests into verified apifire commands without inventing unsupported flags.
Workflow
From zero to repeatable API checks in three steps.
Configure
Set base_url, credentials, auth endpoint, and request YAML files with plain-text config you can version control.
Run
Execute everything with apifire run, or target auth-only / validation-only flows when debugging a pipeline.
Core advantages
Built for teams that want API testing inside the development workflow.
Ship tests with code
Keep API checks in your repo, not in a browser tab.
apifire turns request flows into files under .apifire/, so your setup is diffable, reviewable, and easy to rerun.
Built for auth flows
Run auth once, reuse the token everywhere.
The CLI has a dedicated auth command plus bearer-token config fields like token_path, header_name, and header_prefix.
Fast feedback loop
Initialize, validate, and run from the terminal.
Use apifire init to scaffold a project, apifire validate to catch config mistakes, then apifire run for execution.
Scriptable output
Use token-only auth mode inside your automation.
The auth subcommand supports --token-only, making it straightforward to plug into shell scripts or CI steps.
Command-line workflow
Keep the site anchored in the command-line workflow.
The strongest parts of the product story come from the command line itself. The detailed help, generated scaffold, and real command sequences all live on dedicated inner pages.
Install / discover
$ apifire --help A CLI API testing tool similar to Postman but runs in command line Usage: apifire [OPTIONS] <COMMAND> Commands: init Initialize a new API test project run Run API tests auth Run authentication only to get token validate Validate configuration files