Api Keys Panel
API keys list with prefix-masked values, environment badges, created and last used dates, and a Revoke action.
API keys list with prefix-masked values, environment badges, created and last used dates, and a Revoke action.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Api Keys Panel lists the four active keys for the Acme workspace, each row naming the key (Production server, CI pipeline, Staging deploy, Zapier import legacy), showing the prefix-masked value in monospace (acme_live_4f2k...c8e1), a Live or Test badge, created and last used dates, and a Revoke button. Above the list a callout states the storage model plainly: full keys are shown once at creation, a hash is kept, and losing a key means revoking and rotating it.
Keys are one array, environment drives the badge variant. The callout and the footer note (revocation takes 60 seconds, revoked keys return 401) are the content, not decoration; they cut the most common support questions before they arrive.
Reach for this block on the developer or security settings page, wired to your keys API endpoint and scoped to the authenticated workspace. The Revoke button should call DELETE /api-keys/{id} and remove the row; Generate key should open a dialog that displays the full key once.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the workspace API keys list. Other credential panels:
Tip: Never used is more informative than a blank cell; a key that has never fired is a credential worth reviewing.