# API Keys — Web app

A screen where users generate and manage API keys and other developer-facing credentials needed to integrate the product programmatically.

Source: https://www.checklist.design/web-app/api-keys

## Items

### Key list
A table of all existing API keys showing name, creation date, last used date, and permissions

_Tip: Only show the last few characters after creation for identification without risk of revealing entire key_

### Generate key
A clear way to create a new API key, with the option to give it a name and set its scope or permissions

_Tip: Unnamed keys become impossible to manage as the list grows, so requiring a name before generation is useful_

### Copy key on creation
The full key revealed exactly once immediately after creation, with a prominent copy button

_Tip: Users need to be explicitly told this is the only time the key will be shown in full, following this it will be impossible to copy again_

### Key permissions or scopes
The ability to limit what each key can access (read-only, specific resources, or full access)

_Tip: Least-privilege access is a security best practice, and when fine-grained scopes are easier to set than full-access, more users choose them_

### Revoke key
A clear way to immediately invalidate a key, with a confirmation step before proceeding.

_Tip: Revocation is instant and irreversible, so the confirmation message needs to communicate this clearly, since there is no undo_

### Documentation link
A direct link to API documentation so developers can get started without having to search for it

## License for the Checklist Design collection

Checklist Design collection: https://github.com/Checklist-Design/skills
Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12
Republished under the MIT License. Original checklist text belongs to Checklist Design.

MIT License

Copyright (c) 2026 Checklist Design

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.