API

Writing

Publish, patch, promote, roll back and manage bins over HTTP.

All writes need a secret key (sk_live_…) or a dashboard session. Bodies are JSON, at most your plan's payload size (see Limits). Every write is checked against the bin's schema.

PUT
curl -X PUT "https://api.hotcfg.run/v1/acme/mobile-flags?env=staging" \
  -H "Authorization: Bearer $HOTCFG_SECRET_KEY" \
  -d '{"features": {"checkout_v2": true}}'

# {"bin_id":"mobile-flags","environment":"staging","version":4,"hash":"…"}

Bins

RequestDoes
POST /v1/binsCreate a bin in your key's organization: {"id", "name", "description", "schema", "is_public"}.
GET /v1/binsList bins, most recently updated first, with total. Optional q, updated_after, updated_before, and limit (1–100) with offset.
DELETE /v1/:org/:binDelete the bin with all environments and history.

Versions

RequestDoes
PUT /v1/:org/:bin?env=Publish the body as the next version.
PATCH /v1/:org/:bin?env=Apply a JSON Merge Patch (RFC 7386) to the current version; null deletes a key.
POST /v1/:org/:bin/promoteCopy one environment's current version to another: {"from_env", "to_env"}.
POST /v1/:org/:bin/rollback?env=&to=NPublish version N again, as a new version.
GET /v1/:org/:bin/history?env=List versions, newest first, with authors.
POST /v1/:org/:bin/unpublishTake an environment offline: {"env": "staging"}. History is kept.
DELETE /v1/:org/:bin/environments/:envDelete the environment and its whole history.

Keys

RequestDoes
PATCH /v1/organizations/:id/keys/:key_idRename a key: {"name"}. Its role and limits never change.
POST /v1/organizations/:id/keys/:key_id/rotateReplace a key's secret; the old one stops working at once. Returns the new key, once.

Last updated 5 November 2026