New Item Type recommendation: API Keys

Question

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 FieldsField NameTypePurposeService NameTextIdentifies the platform or API (e.g., “OpenAI API”).API KeyConcealedThe actual secret string; hidden by default, revealable on demand.EnvironmentText/SelectionHelps differentiate between “Production,” “Staging,” or “Development.”Key TypeText/SelectionIdentifies the key’s purpose — e.g., “Secret,” “Public,” “Bearer Token,” “Client Token.”Created DateDateTracks when the key was generated.Recommended Optional FieldsField NameTypePurposeDescriptionText (multiline)Freeform notes about usage, permissions, quotas, etc.Service URL / API Console URLURLDirect link to the managing website or API dashboard.Expiration DateDateUseful for keys with rotation or expiration requirements.Key Owner / Issued ToTextIdentifies who or which system owns the key.Scopes / PermissionsTextLists the granted permissions or access scopes.Rotation ScheduleDate or TextNext planned rotation or rotation policy (“every 90 days”).Linked AccountReference or TextOptional link to the related Login item or user account.TagsText (multiple)Categorization (e.g., “AWS,” “internal,” “low risk”).AttachmentFile (optional)Store related configuration files like .env or key manifests.

Tom · Accepted Answer

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)!

bctoledo · Answer

Thank you. This is what I was looking for.  I can add the other fields manually.

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.

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.

Recommended Required Fields

Recommended Optional Fields

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded