CLI reference

Install, configure, and use the haszno CLI: global flags, output formats, exit codes, and every command group with examples.

Install

The haszno CLI is a Node.js program (Node.js 20 or later). The package is not published on npm ("private": true in package.json). Use one of the methods below.

One-step installer (all three tools)

Installs the CLI, MCP server, and skill together. Requires Node.js 20+, git, and npm.

curl -fsSL https://raw.githubusercontent.com/haszno-labs/haszno-skill/main/install.sh | bash

See Agents overview for what the installer does step by step.

Manual install (CLI only)

npm install -g github:haszno-labs/haszno-cli

Run once without installing

npx -y github:haszno-labs/haszno-cli account ping

Verify installation

haszno --version
# 0.1.0

haszno account ping
# API: OK elérhető

Configuration

The CLI takes its API address and credentials from the --api-url / --api-key flags, from environment variables, or from the config file that haszno login writes. For an interactive machine, log in once:

haszno login --api-url https://haszno.com --api-key <your-api-key>

For scripts, CI and cron jobs, export the variables instead:

export HASZNO_API_URL=https://haszno.com
export HASZNO_API_KEY=<your-api-key>

Environment variables

Precedence

Highest to lowest:

1. --api-url / --api-key flags
2. HASZNO_API_URL, HASZNO_API_KEY, HASZNO_BASIC
3. ARFUTAR_API_URL, ARFUTAR_API_KEY, ARFUTAR_BASIC (legacy)
4. ~/.config/haszno/config.json
5. ~/.config/arfutar/config.json (legacy, read only if the file above does not exist)
6. https://haszno.com, no credentials

An API key is sent as the x-api-key header. HTTP Basic credentials are used only when no API key is found; there is no flag for them.

Two rules keep credentials from reaching the wrong server:

• The config file is read only when neither a flag nor the environment supplies credentials. A key from the environment is never sent to a URL that only the config file names.
• Credentials from the config file are sent only to the URL they were saved for (apiUrl in the file, or https://haszno.com if the file has none). If --api-url or HASZNO_API_URL points to a different server, pass the key for that server explicitly.

If nothing is set, requests are sent without credentials. That is enough for the public demo endpoints.

Config file

haszno login writes ~/.config/haszno/config.json (file mode 600). Both the CLI and the MCP server read it, so one login configures both.

{
  "apiUrl": "https://haszno.com",
  "apiKey": "<your-api-key>"
}

A basicAuth value (user:password) in the file is also honoured. A file that is not valid JSON, or is not a JSON object, is ignored.

Requests

Every request sends Content-Type: application/json, Accept: application/json and User-Agent: haszno-cli/0.1.0. HTTP 429 and 5xx responses and network errors are retried, up to 3 attempts in total, with exponential back-off starting at 500 ms. Each attempt times out after 30 seconds.

Global flags

These flags belong to the root haszno command. You can put them before or after the subcommand (haszno --json products list and haszno products list --json are the same).

Output formats

Without --json: human-readable text and tables. Labels and messages are in Hungarian.

With --json: one JSON document on stdout. List commands print a JSON array, except where a command section below names a wrapper object (catalogue search, ideas list, blog latest). Some commands pretty-print the JSON, others print it on one line; parse it with a JSON parser such as jq, not line by line.

Errors are written to stderr as plain text (usually Hiba: <message>), also in --json mode. The only exception is haszno ideas, which writes {"error": "<message>"} to stderr in --json mode.

Exit codes

Write commands and confirmation

Write commands behave in one of three ways when --yes is missing:

haszno import add writes immediately; it has no confirmation and no --yes flag.

In scripts and agents, always pass --yes to a write command once the user has confirmed the action. Without a terminal, account settings update and feeds import-* exit with code 2, and ideas fill-keywords --json refuses to run.

haszno login

Save the API URL and key to ~/.config/haszno/config.json for the CLI and the MCP server. haszno configure does the same.

Synopsis: haszno login [--api-url <url>] [--api-key <key>]

With flags it saves the given values without prompting, which also works in scripts. Without flags it prompts for the API URL (press Enter to keep the default, https://haszno.com) and the API key; without flags and without a terminal it exits with code 2. Existing values in the file are kept unless you replace them, and the file is written with mode 600.

haszno login --api-url https://haszno.com --api-key <your-api-key>
# Konfigurációs fájl elmentve: /home/you/.config/haszno/config.json

haszno account

haszno account ping

Check API connectivity. /api/health needs no credentials. Exits with 1 if the API does not answer ok.

Synopsis: haszno account ping

haszno account ping

haszno account stats

Print the dashboard summary.

Synopsis: haszno account stats [--json]

haszno account stats --json

JSON output: { products, losing, overMarket, toFix, orders }

See also: haszno account impact · MCP: haszno_account_get_stats

haszno account impact

Print the profit impact for the last N days.

Synopsis: haszno account impact [--days <n>] [--json]

haszno account impact --days 7 --json

JSON output: includes days, extraProfit, baseline, pctGain, orders, autoForwardedOrders

haszno account settings update

Update pricing settings. Write — prompts [y/N] unless you pass --yes. Give at least one of the three flags; the others keep their current values.

Synopsis: haszno account settings update [--undercut-pct <n>] [--min-margin-pct <n>] [--vat-pct <n>] [--yes]

haszno account settings update --undercut-pct 1 --min-margin-pct 10 --vat-pct 27 --yes

haszno products

Your own shop's products and pricing.

The write subcommands prompt [y/N] unless you pass --yes.

haszno products list

Fetch your products and print them.

Synopsis: haszno products list [--all] [--losing] [--over-market] [--cats <names>] [--json]

# Human-readable table
haszno products list

# JSON output — all fields
haszno products list --json

# Include unlisted, filter with jq
haszno products list --all --json | jq '.[] | select(.current.marginPct < 10)'

JSON fields per product (selection): id, sku, name, supplierName, listed, priceGross, costNet, stock, current.marginPct, recommended.priceGross, marketMinGross, marketShop

haszno products update

Synopsis: haszno products update <id> [--price <gross>] [--market-min <gross>] [--market-shop <name>] [--yes]

Give at least one of --price, --market-min, --market-shop; otherwise the command exits with 2.

haszno products apply-prices

Apply the engine's recommended prices. Write — prompts [y/N] unless you pass --yes.

Synopsis: haszno products apply-prices [--ids <id,...>] [--yes] [--json]

# Prompts before changing anything
haszno products apply-prices --ids 1,2,3

# After the user has confirmed
haszno products apply-prices --ids 1,2,3 --yes

JSON output: { changed, total }

haszno catalogue

Search the partner catalogue.

haszno catalogue search

Synopsis: haszno catalogue search [--q <text>] [--cats <keys>] [--partner <id>] [--min-margin <pct>] [--max-price <ft>] [--min-price <ft>] [--in-stock] [--country <code>] [--sort <key>] [--page <n>] [--page-size <n>] [--json]

JSON output: { items, total, facets }. Each item has id (the catalogue product ID that haszno import add expects), name, partnerId, partnerName, categoryKey, wholesaleNet, rrpGross, marginPct, stock, inImportList, inShop.

# Find in-stock garden items with at least 20% margin
haszno catalogue search --cats kert --min-margin 20 --in-stock --json \
  | jq '.items[] | {id, name, marginPct, stock}'

haszno import

Import list: stage catalogue products, then create them in your shop or push them to a connected webshop.

Status values for --status: varakozik, feltoltve, elvetve These are the values the API filters on; the CLI's built-in help text lists varakozik, kuldve, kesz, hiba, which are per-target push states, not item states.

push without --target calls POST /api/import-list/push, which creates the products in your Haszno shop and returns { pushed }. With --target <connectionId> (from haszno connections list) it calls POST /api/connect/stores/<connectionId>/push, which sends them to that connected webshop and returns { pushed, failed, errors }.

# Stage two catalogue products (catalogue product IDs from `catalogue search`)
haszno import add 101 102

# Look up the import list item IDs
haszno import list --status varakozik --json

# Preview: what push would do
haszno import push --ids 5,6

# Create the items in your Haszno shop
haszno import push --ids 5,6 --yes

# Push to a specific connected webshop
haszno import push --ids 5,6 --target 1 --yes

haszno connections

Status values: uj, domain_ok, kapcsolva, hiba

haszno connections list --status kapcsolva --json

haszno proposals

Status values for --status: pending, approved, rejected, rolled_back

Without --yes, approve, reject and rollback print a [DRY-RUN] line and exit with 0.

# List pending proposals
haszno proposals list --status pending --json

# Preview the approval
haszno proposals approve --ids 10,11,12

# Approve after the user has confirmed
haszno proposals approve --ids 10,11,12 --yes
# Jóváhagyva: 3 javaslat (batch: <batchId>)

# Roll back if needed
haszno proposals rollback --batch <batchId> --yes

haszno rules

Automation rules. Every write subcommand prints a [DRY-RUN] preview and exits with 0 unless you pass --yes.

Template keys: keszlet_or, arjavaslat, felar_savok, veszteseg_riasztas. Built-in triggers: feed_import, market_price, manual. The CLI can only create rules from templates; it has no flags for custom conditions or actions.

# Check kill switch
haszno rules automation --json

# Browse templates
haszno rules templates --json

# View execution log
haszno rules runs --limit 10 --json

# Pause automation (without --yes this is only a preview)
haszno rules automation pause --yes

haszno orders

Status values for --status: received, forwarded, shipped, error

ship and demo prompt [i/n] unless you pass --yes.

# Find error-status orders
haszno orders list --status error --json

# Mark shipped
haszno orders ship 42 --yes

haszno peers

P2P partner invites for sharing supplier access with a partner shop.

# Preview (no --yes)
haszno peers invite --supplier 7 --expires 2026-12-01T00:00:00Z

# Create invite
haszno peers invite --supplier 7 --expires 2026-12-01T00:00:00Z --yes

# Accept a received invite code
haszno peers accept INVITE-XYZ --acceptor my-shop --yes

haszno ideas

Product ideas from your products, ranked by trend score and margin (GET /api/recommendations).

JSON output (list): { anchor, geo, total, filtered, items }. Each item has rank, id, sku, name, supplier, stock, costNet, suggestedPriceGross, marginNet, marginPct, trendScore.

haszno ideas list --limit 10 --json | jq '.items[] | {name, trendScore}'

haszno feeds

Feed import and outbound feed URLs.

--supplier and --format are required for import-supplier. Without --file the commands read stdin; because stdin is then not a terminal, pass --yes as well.

urls prints <base URL>/feed/arukereso.xml and <base URL>/feed/google.xml. With --fetch it also downloads them, without sending credentials.

# Import a CSV supplier feed
haszno feeds import-supplier --supplier 3 --format csv --file ./supplier-feed.csv --yes
# Létrehozva   142
# Frissítve    7
# Összesen     149

JSON output: import-supplier → { created, updated, total }; import-market → { matched, total }

haszno blog

JSON output: { posts, total, … }

haszno blog latest --period honap --limit 3 --json

See also

• Agents overview — decision table, one-step installer, safety model
• MCP server — full tool reference for Claude Code and MCP clients
• Authentication — how to get an API key beyond the demo