Create a container registry credential
Store credentials for a private container registry in Runpod for authenticated image pulls while keeping the saved secrets write-only.
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
1 - 191"my-private-registry"
Registry password (write-only, not returned in responses)
1 - 16384Registry username (write-only, not returned in responses)
1 - 191