Skip to main content
PATCH
Update a container registry credential
Required API key scope: secrets:write

Authorizations

Authorization
string
header
required

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.

Path Parameters

id
string
required

Body

application/json
password
string
required

New registry password (write-only, not returned in responses)

Required string length: 1 - 16384
username
string
required

Registry username to store with the new password (write-only, not returned in responses)

Required string length: 1 - 191

Response

OK

id
string
required
Example:

"reg_abc"

name
string
required
Example:

"my-private-registry"

Last modified on November 18, 2026