API keys page design examples

An API keys page lets developers create, review and revoke credentials safely. Our examples show keys with scopes and last-used times, a one-time key reveal, a create key action and usage limits, designed for a fictional workspace product on web and mobile in eight visual styles with light and dark themes. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

API keys design tips

Show the full secret only once at creation with a copy button, and warn clearly that it cannot be viewed again.
Let people name each key and see its scopes, so they know which integration will break if it is revoked.
Display last-used times so unused keys are easy to spot and remove.
Mask stored keys to a short recognisable prefix or suffix, enough to match them against configuration files.

Questions

Why are API keys only shown once?

Showing a secret once means the service can store only a hashed version, so a database leak does not expose usable keys. It also encourages people to put the key straight into a secrets manager. If it is lost, they create a new one.

What should an API keys table include?

Key name, a masked identifier, scopes or permissions, creation date, last used time and who created it. Row actions should include revoke and, where supported, rotate. Expiry dates are worth showing if keys can expire.

How should key revocation be designed?

Ask for confirmation that names the key and states that applications using it will stop working immediately. Revocation should take effect at once. Supporting several active keys lets teams rotate credentials by creating a new key before revoking the old one.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.