Create a network volume
Create a persistent Runpod network volume with a name, size, data center, and storage tier for use by Pods and Serverless workers.
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
Data center in which to create the volume
1"EU-RO-1"
Human-readable name
1"my-dataset"
Storage to allocate in GB
10 <= x <= 409650
Storage tier for the volume. Optional. When omitted, the volume is provisioned using the requested data center's default (primary) storage tier. HIGH_PERFORMANCE provisions a high-performance (HPS) volume; STANDARD provisions a standard volume. A volume's tier is immutable after creation.
STANDARD, HIGH_PERFORMANCE Response
Created
Unique network volume identifier
"agv6w2qcg7"
Human-readable name (not required to be unique)
"my-dataset"
Allocated storage in GB
10 <= x <= 409650
Data center location; immutable after creation
"EU-RO-1"
Storage tier of this volume. Set at creation and immutable.
STANDARD, HIGH_PERFORMANCE Cost center this resource's spend is attributed to. Absent when the resource is not attributed to a cost center, or when the caller lacks permission to view cost centers. Managed through /v2/cost-centers.
The tags on this resource that are visible to the caller. Keys and values are returned exactly as stored. Tags under the reserved runpod: prefix, such as the cost center, are never listed here. Absent when the resource's tags are unavailable to the caller; an empty array means none are visible.