Update a global volume
Rename a Runpod global volume.
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.
Path Parameters
Global volume identifier
Body
Only the provided fields are updated. At least one field must be present; an empty body is rejected.
New human-readable name, 1–191 characters with at least one non-whitespace character. Leading and trailing whitespace is trimmed.
1 - 191[^\p{Z}\t-\r
]"renamed-volume"
Response
OK
Unique global volume identifier
"gsb_abc"
Human-readable name (not required to be unique)
"training-data"
When the volume was created
ID of the user who created the volume, if known
"user_123"