Skip to content

Commit

Permalink
Update content/docs/manage/api-keys.md
Browse files Browse the repository at this point in the history
Co-authored-by: Daniel <[email protected]>
  • Loading branch information
bgrenon and danieltprice authored Dec 13, 2024
1 parent 3c0d7a4 commit 4b77a85
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/docs/manage/api-keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ While there is no strict limit on the number of API keys you can create, we reco
You'll need to create your first API key from the Neon Console, where you are already authenticated. You can then use that key to generate new keys from the API.

<Admonition type="note">
When creating API keys from the Neon Console, the secret token will be displayed only once. Copy it immediately and store it securely in a credential manager (like AWS Key Management Service or Azure Key Vault) - you won't be able to retrieve it later. If you lose an API key, you'll need to revoke it and create a new one.
When creating API keys from the Neon Console, the secret token will be displayed only once. Copy it immediately and store it securely in a credential manager (like AWS Key Management Service or Azure Key Vault) you won't be able to retrieve it later. If you lose an API key, you'll need to revoke it and create a new one.
</Admonition>

### Create a personal API key
Expand Down

0 comments on commit 4b77a85

Please sign in to comment.