Skip to main content
POST
Create a global volume

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.

Body

application/json
name
string
required

Human-readable name, 1–191 characters with at least one non-whitespace character. Leading and trailing whitespace is trimmed.

Required string length: 1 - 191
Pattern: [^\p{Z}\t-\r…]
Example:

"training-data"

Response

Created

id
string
required

Unique global volume identifier

Example:

"gsb_abc"

name
string
required

Human-readable name (not required to be unique)

Example:

"training-data"

createdAt
string<date-time>
required

When the volume was created

createdByUserId
string | null
required

ID of the user who created the volume, if known

Example:

"user_123"

Last modified on October 13, 2026