CLI

# hotcfg get

Print a bin's payload, a pinned version of it, or the result of a jq query.

usage

```
hotcfg get <bin_id> [--env <env>] [--v <version>] [--query <jq>]
```

Prints the payload of one environment. Public bins need no key; name them with their organization.

terminal

```
$ hotcfg get acme/mobile-flags --env production
{"features":{"checkout_v2":true,"new_onboarding":false},"limits":{"max_upload_mb":50}}

$ hotcfg get mobile-flags --query .features.checkout_v2
true
```

On a terminal the JSON is indented; piped, it's printed as the API sent it.

## Flags

| Flag | Default | Description |
| --- | --- | --- |
| `--env` | `production` | `production`, `staging` or `development`. |
| `--v` | `latest` | A version number, such as `3` or `v3`, or `latest`. |
| `--query` |  | A jq filter run by the API. See [Querying with jq](https://hotcfg.run/docs/guides/queries). |

## Without a key

A private bin read without a key answers like a missing bin, so the CLI adds a hint:

terminal

```
$ hotcfg get acme/private-flags
error: bin not found (HTTP 404, not_found)
hint: if the bin is private, it needs an API key: --key, $HOTCFG_API_KEY or 'hotcfg login'
```

## In scripts

terminal

```
# Fail a release build if the kill switch is on
if [ "$(hotcfg get acme/mobile-flags --query .features.maintenance)" = "true" ]; then
  echo "maintenance mode is on in production" >&2; exit 1
fi

# Save production as the defaults bundled with the app
hotcfg get acme/mobile-flags --env production > app/defaults/flags.json
```

Last updated 5 November 2026
