Configuration - Qonto

The CLI works without any configuration. When you want different defaults, set them in a configuration file or in environment variables. When the same setting is given in several places, the first one wins:

A flag on the command (-o yaml)
An environment variable (QONTO_CLI_OUTPUT=yaml)
The configuration file (output: yaml)
The built-in default

The configuration file

The file is ~/.config/qonto/config.yaml on every system (%USERPROFILE%\.config\qonto\config.yaml on Windows). Manage it with qonto config:

qonto config set output json   # write a value
qonto config get output        # read it back
qonto config unset output      # remove it
qonto config list              # every effective setting, wherever it comes from
qonto config path              # where the file is

Key	What it sets	Default
`output`	Output format: `table`, `json`, `yaml`, or `raw`.	`table` on a terminal, `json` otherwise
`sca_method`	Strong Customer Authentication method: `paired-device`, `passkey`, or `sms-otp`.	`paired-device`
`scopes`	Scopes requested by `qonto auth login`, comma- or space-separated.	Every scope the CLI’s commands use

qonto config --help lists every key. The file never contains a token or a secret: the session is in your credential store.

Environment variables

Variable	What it does
`QONTO_CLI_OUTPUT`	Same as `output`.
`QONTO_CLI_SCA_METHOD`	Same as `sca_method`.
`QONTO_CLI_SCOPES`	Same as `scopes`.
`QONTO_CLI_STORE_CLEARTEXT`	Set to `1` to use a session kept in a file instead of the credential store, see Machines without a credential store. Cannot be set in the configuration file.
`QONTO_CLI_ACCESS_TOKEN`	Use this access token instead of the stored session. Never saved.
`QONTO_CLI_CONFIG_DIR`	Use another directory than `~/.config/qonto`. `XDG_CONFIG_HOME` is honored too.
`QONTO_CLI_CACHE_DIR`	Where the CLI caches the result of its version check.
`QONTO_CLI_NO_UPDATE_CHECK`	Set to `1` to skip the daily version check.
`NO_COLOR`	Disable colors, like `--no-color`.

Version check

Once a day, the CLI reads https://mcp.qonto.com/cli/manifest.json to learn which versions are current. It then prints, on standard error:

a one-line notice when a newer version is available;
a warning when your version is deprecated or below the minimum supported version, with the date after which it will stop working.

After that date, an unsupported version refuses to run and exits with code 3. Update to continue. The check is a plain download of that file: it sends no token and nothing about your account.