Skip to main content
Manage API keys from the CLI.
For CI jobs, cloud services, and Kubernetes pods, use workload identity federation instead of an API key. There’s no secret to store, and the credential expires in minutes. Service accounts, issuers, and federation rules are managed from the dashboard.

kernel api-keys create

Create an API key. By default, the new key is org-wide. Pass --project-id to create a key whose own access is scoped to that project.
--project-id controls the access scope of the new API key. The global --project flag only scopes the CLI request you’re making.

kernel api-keys list

List API keys in the authenticated organization. API keys are masked. The list shows active keys: keys that are neither deleted nor expired.

kernel api-keys get <id>

Show one API key by ID. The response includes the masked key and metadata, not the plaintext key.

kernel api-keys update <id>

Rename an API key.

kernel api-keys rotate <id>

Issue a replacement API key. The rotated key keeps working for a grace period so you can migrate callers without downtime.
Save the new plaintext key when you rotate it. Kernel won’t return it again. With --expire-in-days 0, the old key’s associated browsers are ended asynchronously and their unsaved profile changes are discarded. A grace-period expiry doesn’t end existing browsers.

kernel api-keys delete <id>

Delete an API key. Its associated browsers are ended asynchronously, and unsaved profile changes in those browsers are discarded.
Automatic cleanup only covers browsers associated with the key. Some older browsers may be unaffected; delete those browsers directly. See API key expiry and revocation.

Aliases

You can also use kernel api-key, kernel apikeys, or kernel apikey.