Create a secret
Create an encrypted Runpod account secret that Pods, Serverless endpoints, and templates can reference from environment variables at boot.
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.
Body
Unique name for the secret — referenced from environment variables as {{ RUNPOD_SECRET_<name> }}; immutable after creation. Maximum 191 characters, must start with a letter or underscore, and may contain letters, digits, and _.-/. Names beginning with the reserved prefix RUNPOD are rejected (case-insensitive).
1 - 191^[a-zA-Z_][a-zA-Z0-9_.\-/]*$"hf-token"
Response
Created
An account-scoped secret: an encrypted string stored by Runpod, referenced from pod, serverless, and template environment variables with the {{ RUNPOD_SECRET_<name> }} placeholder, substituted with the secret's value when the pod or worker boots. The value is write-only and never returned by the API.