Answer: After deleting the compromised key, you can generate a new API key by clicking on the "Create key" button on the same API keys page (platform.claude.com/settings/keys), and you should save this key somewhere secure such as a secrets management system. Status: Confirmed Entry: tool/claude-apps/permissions-and-security/create-new-api-key Revision: 2 Digest: sha256:84d6d40c9f549c4e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:01:47Z Last changed: 2026-11-20T12:13:51Z (Action to delete key: — → Delete API key) Last verified: 2026-11-20T12:13:51Z Next check: 2026-11-21T12:13:51Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Action to create new key | Create key | [1] | 2026-11-20 API keys page | platform.claude.com/settings/keys | [1] | 2026-11-20 Action to delete key | Delete API key | [1] | 2026-11-20 Secure storage recommendation | secrets management system | [1] | 2026-11-20 Sources: [1] Anthropic. "What should I do if I suspect my API key has been compromised? | Claude Help Center". https://support.claude.com/en/articles/8384961-what-should-i-do-if-i-suspect-my-api-key-has-been-compromised Role: primary. Accessed: 2026-11-20T12:13:51Z Quote: "You can generate a new API key by clicking on the "Create key" button on the same page" (Supports: Action to create new key) Quote: "going to the API keys page (platform.claude.com/settings/keys)" (Supports: API keys page) Quote: "selecting "Delete API key."" (Supports: Action to delete key) Quote: "make sure to save this key somewhere secure, such as a secrets management system" (Supports: Secure storage recommendation) Snapshot SHA-256: e41c4646e623101839d7bf11e13dfe2dc1e0d53ec5f6fe6999ab28abcb7578e7 (captured 2026-11-19T12:09:53Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:09:54Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:13:51Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:13:51Z Last attempt: 2026-11-20T12:13:51Z Notes and limitations: Extracted automatically from a single official source (section "What should I do if I suspect my API key has been compromised?"). Related: https://latestn.com/tool/claude-apps/permissions-and-security/csam-match-consequences What happens when an image I send to Claude matches known CSAM? https://latestn.com/tool/claude-apps/permissions-and-security/custom-connector-security-privacy What are the security and privacy considerations for custom connectors in Claude? https://latestn.com/tool/claude-apps/permissions-and-security/cyber-verification-all-access-requirements What security requirements must a customer meet for all Cyber Verification Program access levels in Claude? https://latestn.com/tool/claude-apps/permissions-and-security/control-user-skill-creation How do I control whether users in my Claude organization can create their own skills? https://latestn.com/tool/claude-apps/permissions-and-security/cowork-protect-from-attackers How can I protect myself from malicious attackers when using Claude Cowork? https://latestn.com/tool/claude-apps/permissions-and-security/cowork-safety-measures What safety measures does Claude Cowork have to protect me? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:13:51Z | changed | Action to delete key: — → Delete API key | [1] 2026-11-20T12:13:51Z | changed | Action to create new key: — → Create key | [1] 2026-11-20T12:13:51Z | changed | Delete action: Delete API key → — | [1] 2026-11-20T12:13:51Z | changed | New key creation method: Create key → — | [1] 2026-11-13T03:01:47Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/permissions-and-security/create-new-api-key/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/create-new-api-key POST: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/create-new-api-key with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/permissions-and-security/create-new-api-key?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I create a new Claude API key after deleting a compromised one? Revision 2, last verified 2026-11-20T12:13:51Z. https://latestn.com/tool/claude-apps/permissions-and-security/create-new-api-key (accessed 2026-11-21T10:02:38Z). @misc{LatestN_tool_claude_apps_permissions_and_security_create_new_api_key_r2, title = {How do I create a new Claude API key after deleting a compromised one?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/permissions-and-security/create-new-api-key}}, note = {Revision 2; digest sha256:84d6d40c9f549c4e; last verified 2026-11-20T12:13:51Z; accessed 2026-11-21T10:02:38Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/permissions-and-security/create-new-api-key