Blow the conch.
Run your APIs.

Sankh is a very lightweight request manager. A collection is a plain folder of .sh files, each holding one curl command. One binary runs them in CI or serves a small web UI, and the desktop app opens the same UI in a native window.

Then install it with sudo apt install ./Sankh-linux-amd64.deb.

Get started Install guide GitHub

pets/02-create.sh
#!/usr/bin/env bash
# @name Create pet
# @tags smoke
# @expect status 201
# @expect json .name == "Rex"
# @capture PET_ID=.id
curl -sS "$BASE_URL/pets" \
  -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"name":"Rex"}'

A collection is a folder of curl

Annotations live in comments, so every file is still a curl command you can run on its own. Sankh never runs it: it reads the command and sends the request itself. Your API collection is a git repo that runs anywhere. The UI is optional.

Layout
my-api/
  sankh.toml
  environments/
    dev.env
    ci.env
  auth/01-login.sh
  pets/01-list.sh
  pets/02-create.sh
Works without Sankh
set -a; . environments/dev.env; set +a
sh pets/02-create.sh
sankh run
$ sankh run examples/petstore --env dev
sankh · petstore · env dev (6 requests)
✓ Log in  200  38ms  auth/01-login.sh
    captured TOKEN=***
✓ List pets  200  6ms  pets/01-list.sh
✓ Create pet  201  7ms  pets/02-create.sh
    captured PET_ID=1
✓ Get pet  200  5ms  pets/03-get.sh
✓ Delete pet  204  5ms  pets/04-delete.sh
✓ Deleted pet is gone  404  4ms  pets/05-get-deleted.sh

6 passed  72ms

Run it in CI, a browser, or a window

Built for CI

sankh run filters by folder and tag, writes JUnit or JSON reports, and exits non-zero on failure. Values captured from one response feed the next request.

An optional web UI

sankh serve opens a file tree, form and raw editors, and live results. The server runs the requests, not the browser, so there are no CORS workarounds.

A desktop app

The same UI in a native window for macOS, Windows and Linux, with a native folder picker. It edits the same files and runs requests on your machine. Download

The Sankh web UI showing the petstore collection, the Create pet request editor, and a passing run
sankh serve examples/petstore

All your collections, side by side

Plain files in git, no proprietary export format. Keep several collections open at once, each with its own environments and captured values.

Workspaces

sankh workspace add keeps folders in your workspace, so plain sankh serve and the desktop app open them all. Removing one only unlinks it.

Scratch

A built-in collection for trying requests without a folder. Paste a curl command, run it, and Copy to a real collection when it is worth keeping.

Import from Postman

sankh import postman turns a collection and its environments into .sh files. Common test scripts become assertions; secrets never reach disk.

Workspaces and Scratch · Importing from Postman

Drop it into any pipeline

Install with one line, run the smoke folder, publish a JUnit report. Exit codes tell your CI exactly what went wrong.

ExitMeaning
0All requests passed
1An assertion or capture failed
2A file has an error; nothing was sent
3A request could not be sent (DNS, TLS, timeout)
GitHub Actions
- run: curl -fsSL https://sankh.dev/install.sh | sh
- run: >-
    sankh run . --env ci --folder smoke
    --report junit
  env:
    TOKEN: ${{ secrets.API_TOKEN }}
More on running in CI

Safe by default

Files never execute

No shell, no curl process. Sankh parses each command, rejects pipes and unknown flags with a precise error, and checks every file before sending anything.

Secrets redacted

Values of variables named like TOKEN, SECRET, KEY or PASSWORD are replaced with *** in CLI output, CI reports, and MCP results.

Local first, no telemetry

The UI binds to 127.0.0.1 and rejects foreign hosts and cross-origin calls. Sankh makes no network requests other than the ones in your files.

Secrets and safety