Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Server → Attach Volume
AI-generatedSummary
Attach the specified volume to a server in the selected data center by sending its volume ID in the request body. The operation also supports optional request tracking details and response headers in its output.
Inputs
- Datacenter ID (required) — ID of the data center containing the server.
- Server ID (required) — ID of the server to attach the volume to.
- Volume ID (required) — ID of the volume to attach; sent as the request body's
idfield. - Include Request Status — When enabled, include the async request tracking ID and status URL returned by the API.
- Include Response Headers — When enabled, include response headers and status code, with the response body nested under
body. - Request Options — Optional batching, SSL certificate validation, HTTP proxy, and request timeout settings.
Output shape
A single response item from the attach-volume request.
The operation is asynchronous. Optional request tracking data may be included when enabled. With response headers enabled, the response body is nested under
bodyalongsideheadersandstatusCode.