Posting
A terminal-based HTTP client for building and sending HTTP, GraphQL and gRPC requests, with requests stored locally as YAML files.
Tested on Linux
Use it
Linux x86_64
You need first
- Runtimes:
go>=1.25.5 (for go install)
Download v3.0.0-beta.1 linux_amd64 release archive, verify checksum, install binary to ~/.local/bin
mkdir -p /tmp/posting && cd /tmp/posting && curl -fsSLO https://github.com/darrenburns/posting/releases/download/v3.0.0-beta.1/posting_3.0.0-beta.1_linux_amd64.tar.gz && curl -fsSLO https://github.com/darrenburns/posting/releases/download/v3.0.0-beta.1/checksums.txt && sha256sum --ignore-missing -c checksums.txt && tar xzf posting_3.0.0-beta.1_linux_amd64.tar.gz && mkdir -p ~/.local/bin && install -m755 posting ~/.local/bin/posting
Check that it works
posting --helpThe output should contain “A terminal HTTP client.”.
First thing to try
mkdir -p /tmp/srv /tmp/coll/http /tmp/coll/gql && cat > /tmp/srv/server.py <<'EOF'
import json
from http.server import BaseHTTPRequestHandler, HTTPServer
class H(BaseHTTPRequestHandler):
def _send(self, obj):
b = json.dumps(obj).encode()
self.send_response(200); self.send_header("Content-Type", "application/json")
self.send_header("Content-Length", str(len(b))); self.end_headers(); self.wfile.write(b)
def do_GET(self):
self._send({"path": self.path, "data": {"users": [{"id": 1, "role": "user"}, {"id": 42, "role": "admin"}]}})
def do_POST(self):
body = json.loads(self.rfile.read(int(self.headers.get("Content-Length", 0))) or b"{}")
self._send({"data": {"user": {"name": "Ada", "id": body.get("variables", {}).get("id")}}, "echo_query": body.get("query")})
HTTPServer(("127.0.0.1", 8765), H).serve_forever()
EOF
cat > /tmp/coll/posting.env <<'EOF'
HOST=127.0.0.1
PORT=1
API_PATH=/api/v1
EOF
cat > /tmp/coll/dev.env <<'EOF'
PORT=8765
BASE_URL="http://${HOST}:${PORT}${API_PATH}"
EOF
cat > /tmp/coll/http/01-list.posting.yaml <<'EOF'
name: List users
method: GET
url: ${BASE_URL}/users
captures:
ADMIN_ID: data.users[?(@.role == "admin")].id
EOF
cat > /tmp/coll/http/02-get.posting.yaml <<'EOF'
name: Get admin
method: GET
url: ${BASE_URL}/users/${ADMIN_ID}
EOF
cat > /tmp/coll/gql/01-user.posting.yaml <<'EOF'
name: Get user
kind: graphql
url: ${BASE_URL}/graphql
graphql:
query: |
query User($id: ID!) {
user(id: $id) { name }
}
variables: |
{"id": "7"}
operation_name: User
EOFpython3 /tmp/srv/server.pyposting run -c /tmp/coll http --env dev --jsonRun posting in a terminal to open the request editor.
What it does
- Send HTTP, GraphQL and gRPC requestsTested
How to use it
- Save each request as a
.posting.yamlfile in a folder inside your collection directory, and put variables in.envfiles there. - Run
posting run -c <collection> <folder> --env <env> --jsonto send every request in that folder. - Check the JSON output for each request's URL and the count of passed requests.
- Save each request as a
- Work on several requests in tabsNot tested
- Explore responses with a JSON tree and JSONPathNot shown working
- Manage layered environments and variablesNot shown working
How far pickfit got
Linux x86_64
- Installs
- Starts
- 1 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- send and test HTTP API requests from the terminal over SSH
- import curl commands and export requests as curl
- import API collections from OpenAPI, Postman and Bruno
- filter JSON responses with JSONPath
An alternative to Postman and Insomnia.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version 3.0.0-beta.1
Differences the test machine hit
- README: Install with Homebrew or `go install` (Go 1.25.5+)
In the test: The Linux release archive posting_3.0.0-beta.1_linux_amd64.tar.gz from GitHub releases contains a standalone binary; no Go toolchain needed - README: Only usage example is `posting` (full-screen TUI)
In the test: Headless testing uses `posting run -c DIR PATH --env NAME --json`, documented in --help and docs/guide/running.md, not in the README