Galanthus CLI Reference

This is the reference for gln, the Galanthus banking CLI. Each leaf command has its own page with a fixed section structure: Synopsis, Options, Description, Requirements, Status and exit codes, Examples, and where relevant Notes.

Synopsis

gln [global-options] <command> [args]

Global options

Profile resolution order: --profile <name>, then the configured default profile.

Diagnostics

The JSON envelope on stdout is the authoritative result of every command. Two global flags add diagnostic detail when investigating a failure or attaching information to a support request:

• --verbose writes human-readable trace lines to stderr, including protocol step boundaries and decision points.
• --dump-dir <path> writes raw request and response payloads to that directory in their native form (FinTS segments, EBICS XML, REST JSON). Use it only for a narrow reproduction window when the JSON envelope and verbose trace are not enough.

The JSON envelope, the stderr trace, and the dumped payloads are independent: stdout stays parseable when the other two are enabled, and dumps remain useful even without --verbose. Raw dumps can contain account identifiers, names, balances, access tokens, TAN challenge data, and other secrets. Keep them local by default, redact or minimize before sharing, transfer them only over an approved secure channel, and delete them as soon as the investigation no longer needs them.

Source builds may include the C API scripted test transport when compiled with GALANTHUS_ENABLE_TEST_TRANSPORT=ON, which is the default for developer builds. The CLI does not expose --scripted-* flags; fixture playback for operational CLI paths goes through the GALANTHUS_CAPI_TEST_* environment before backend open. Binaries distributed for real banking use must be configured with -DGALANTHUS_ENABLE_TEST_TRANSPORT=OFF so scripted response injection is not compiled in.

JSON envelope

Every command writes a single JSON object to stdout. The top-level fields are:

• status - one of ok, error, rejected, action_required, follow_up_required. The status drives both the exit code and the follow-up workflow.
• result - the typed result payload. Each command page lists the populated keys under "Result keys".
• action - present when status is action_required. Carries the details needed to resume (for example details.resume_file).
• next_steps - optional guidance string for human operators.
• warnings - optional array of compatibility or advisory warnings.

Use the JSON envelope, not stderr or exit codes alone, to drive scripted workflows.

Shell conventions

All per-command examples in this reference use PowerShell, matching the README. The translation rule is mechanical: PowerShell backtick line continuation maps to bash backslash continuation; flag names and values are identical.

gln --profile demo profile show

gln --profile demo profile show

Exit codes and status values

The JSON envelope's status field carries the workflow contract; exit codes are additive convenience for shell scripting.

Backend Capability Overview

The public CLI surface below documents supported commands. Profile management and versions commands perform local work; provider commands resolve the active profile before dispatching through the backend path.

By task

• Manage local profile registrations: profile init, profile list, profile show, profile set-default, profile remove
• Run EBICS setup and key lifecycle workflows: profile status, profile bootstrap, profile bank-keys download, profile bank-keys show, profile bank-keys verify, profile bank-keys reset, profile client-keys reset, profile brief ini, profile brief hia
• Run Revolut OAuth setup workflows: profile auth login revolut, profile auth status revolut
• Run Revolut recipient and payment-draft workflows: revolut recipients list, revolut recipients create, revolut recipients delete, revolut payment-drafts list, revolut payment-drafts show, revolut payment-drafts create, revolut payment-drafts delete
• Run Wise token setup workflows: profile auth login wise, profile auth status wise
• Approve plugin bundles after operator digest verification: plugin approve
• Show local version information: versions
• Read account data, submit supported write operations, and manage TAN follow-up workflows through the active backend paths.

All commands

Profiles

Read

Revolut provider

TAN

Write

transfers sepa, transfers batch, direct-debits create, and direct-debits batch submit through FinTS or EBICS and support dry-run request previews. transfers instant, standing-orders add, standing-orders modify, standing-orders delete, and prepaid-topup submit through the FinTS backend.

Utility

See also

• Troubleshooting - cross-cutting failure modes that affect more than one command.
• Library reference - C ABI setup, continuation handling, and embedding guidance.