Developer
A developer profile with API keys, access tokens, connected apps, and usage notes. Use it on settings pages where engineers manage their integrations.
A developer profile with API keys, access tokens, connected apps, and usage notes. Use it on settings pages where engineers manage their integrations.
Search blocks by description or jump to a page.
Developer Settings is a focused settings panel for engineers managing their integration credentials. A page heading with a "View Documentation" button sits at the top, followed by two stacked cards. The first card lists API keys, each showing its name, a masked key string with a copy button, creation date, last used time, an Active badge, and Rotate plus Revoke actions. The second card lists webhook endpoints, each with the target URL, an Active or Failed status badge, the subscribed event names as secondary badges, and the last delivery result, along with a Configure button. A security alert banner closes the layout reminding the user to protect their credentials.
The two cards are independent sections. You can remove the webhooks card if your product does not support them, or add more entries to either list. All copy including key names, event strings, and the alert text is plain data you can swap without affecting layout.
Reach for this block on the developer or integrations tab of a settings area, where the person signed in needs to see and manage their API keys alongside any webhooks they have registered. For an AI assistant product this is exactly the screen where a builder grabs their production key before wiring up their first prompt call. It handles both credential management and webhook health in one place, so you avoid splitting those concerns across two separate routes.
A natural flow around it on an Application page:
Before
After
Each card maps to a distinct concern, so you can tailor them separately:
Tip: keep the event badge list to two or three items per webhook row so the status badge and URL remain easy to scan at a glance.