CLI

hotcfg bins

List your organization's bins, or create one with a schema.

usage
hotcfg bins list [--json]
terminal
$ hotcfg bins list
ID            NAME          ACCESS           ENVIRONMENTS               UPDATED
mobile-flags  Mobile flags  public, schema   production v4, staging v3  2026-11-05 22:57
pricing       Pricing       public           production v1              2026-11-05 22:57
web-banner    Web banner    public           production v1              2026-11-05 22:57

A limited key lists only its bins and environments. --json prints the API's response.

bins create

usage
hotcfg bins create <bin_id> [--schema <file>] [--public] [--name <name>] [--description <text>]
terminal
$ hotcfg bins create mobile-flags --public --schema schema.json --name "Mobile flags"
✓ Created bin mobile-flags
  name     Mobile flags
  access   public: anyone can read it
  schema   schema.json
  next     hotcfg push config.json --bin mobile-flags --env staging
FlagDefaultDescription
--schemanoneA JSON Schema file every version must match.
--publicprivateLet anyone read the bin without a key. Public bins are cached at the edge. Required on Free.
--namethe idThe name shown in the dashboard.
--descriptionnoneUp to 1,000 characters.

An id is 1–64 characters of a-z, 0-9, - and _, starting with a letter or digit, unique in your organization. It's part of the read URL and can't be changed. Creating bins needs a key without bin or environment limits.

Without --public the bin is private: reads need a key. Private bins are part of Pro. On Free, bins create without --public fails with 403 private_bins_require_pro; add --public, and keep secrets out of the bin, since anyone with its URL can read it.

Last updated 10 November 2026