Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
New Item Type recommendation: API Keys
I would like to see a new item type: API Key for securely storing machine-to-machine credentials used in development and automation. It would include fields for the key, environment, service name, expiration, rotation schedule, and scope. This would help developers separate API credentials from personal passwords, reduce misuse, and support compliance best practices. This important because API keys are generally created and shared only once. Being able to store these safely in 1Password would be a big help. By having a new Item type, these can be more easily browsed as a group.
Recommended Required Fields
| Field Name | Type | Purpose |
|---|---|---|
| Service Name | Text | Identifies the platform or API (e.g., “OpenAI API”). |
| API Key | Concealed | The actual secret string; hidden by default, revealable on demand. |
| Environment | Text/Selection | Helps differentiate between “Production,” “Staging,” or “Development.” |
| Key Type | Text/Selection | Identifies the key’s purpose — e.g., “Secret,” “Public,” “Bearer Token,” “Client Token.” |
| Created Date | Date | Tracks when the key was generated. |
Recommended Optional Fields
| Field Name | Type | Purpose |
|---|---|---|
| Description | Text (multiline) | Freeform notes about usage, permissions, quotas, etc. |
| Service URL / API Console URL | URL | Direct link to the managing website or API dashboard. |
| Expiration Date | Date | Useful for keys with rotation or expiration requirements. |
| Key Owner / Issued To | Text | Identifies who or which system owns the key. |
| Scopes / Permissions | Text | Lists the granted permissions or access scopes. |
| Rotation Schedule | Date or Text | Next planned rotation or rotation policy (“every 90 days”). |
| Linked Account | Reference or Text | Optional link to the related Login item or user account. |
| Tags | Text (multiple) | Categorization (e.g., “AWS,” “internal,” “low risk”). |
| Attachment | File (optional) | Store related configuration files like .env or key manifests. |
You probably want an extension of the current 'API-credentials ' item I guess? That has most of them set (though it would be nice to have some of the missing ones you suggest)!
