Skip to main content
Runpod Documentation home page
Docs
Copy page
Search...
Runpod Documentation home page
Search...
Navigation
Troubleshooting
Leaked API Keys
Get started
Introduction
Quickstart
Concepts
Manage accounts
Manage API keys
Choose a workflow
Serverless
Overview
Pricing
Workers
Endpoints
vLLM workers
Load balancing endpoints
Development
Pods
Overview
Pricing
Choose a Pod
Manage Pods
Connect to Pods
Storage
Templates
Storage
Network volumes
S3-compatible API
Public Endpoints
Overview
Model reference
NEW
Instant Clusters
Overview
Slurm Clusters
Deployment guides
Fine-tuning
Fine-tune a model
Hub
Overview
Hub publishing guide
Revenue sharing
Reference
Billing information
Referral programs
Security and compliance
GPU types
CPU types
Troubleshooting
Zero GPU Pods
JupyterLab checkpoints folder
Leaked API Keys
Storage full
502 errors
JupyterLab server token authentication
Manage payment card declines
Integrations
Migrations
Intro to containers
Hosting
GraphQL Spec
Runpod console
runpod/docs
On this page
Disable
Revoke
Troubleshooting
Leaked API Keys
Leaked API keys can occur when users accidentally include a plain text API key in a public repository. This document provides guidance to help you remediate a compromised key.
​
Disable
To disable an API key:
From the console, select
Settings
.
Under
API Keys
, select the toggle and select
Yes
.
​
Revoke
To delete an API key:
From the console, select
Settings
.
Under
API Keys
, select the trash can icon and select
Revoke Key
.
Was this page helpful?
Yes
No
Suggest edits
Raise issue
JupyterLab checkpoints folder
Storage full