Automating Publishing With Site API Keys
Site API keys let agencies and developers publish and manage a Piskes site programmatically, scoped to one site and owner-only to mint.
Agencies and developers managing Piskes sites at any scale have asked for a way to publish and manage a site without a human clicking through the UI every time. Site API keys, available today, are that answer.
How it works
From a site's settings, an owner can mint an API key scoped to that one site. Keys default to read-only — a key that can also publish has to be granted the write scope explicitly, never handed out by omission. The full key is shown exactly once at creation time; only its hash is stored afterward, so losing it means generating a new one, not recovering the old one.
Why it's owner-only
Unlike most settings on a site, minting an API key is restricted to owners, not editors. The reasoning is direct: a key with write access can publish the site on its own, which is the same blast radius as deleting it outright. That's not a permission level Piskes hands to anyone with edit access by default.
What it's for
A key authenticates against the public API (/api/v1/public/sites/...) — the same surface used for reading pages, running audits, and checking deploy history. For an agency running CI against a client's site, or a script that publishes on a schedule, this replaces logging in as that client every time with a credential scoped to exactly one site and exactly the actions it's allowed to take.
Manage keys from Site Settings → API Keys. Existing sites can start using this today with no migration required.