Create a volume
POST/compute/{connection_id}/volume
Parameters
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection
Payload
idstring
Unique identifier for the volume
created_atdate-time
When the volume was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
When the volume was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
Display name of the volume
type enum
Valid values:
"STANDARD"
"HIGH_PERFORMANCE"
"SHARED"
"LOCAL"
"OTHER"
The kind of volume
status enum
Normalized volume status
size_mbnumber
Provisioned size in MiB
used_mbnumber
Used space in MiB
region_idstring
The region the volume lives in
availability_zonestring
The availability zone within the region, where the vendor places volumes per zone
instance_idsstring array
Instances the volume is mounted on
Returns
| Response field | Type | Required | Description |
|---|---|---|---|
id | string | No | Unique identifier for the volume |
created_at | string (date-time) | No | When the volume was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
updated_at | string (date-time) | No | When the volume was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
name | string | No | Display name of the volume |
type | enum | No | The kind of volume Values: STANDARD, HIGH_PERFORMANCE, SHARED, LOCAL, OTHER |
status | enum | No | Normalized volume status Values: CREATING, AVAILABLE, IN_USE, DELETING, ERROR, OTHER |
size_mb | number | No | Provisioned size in MiB |
used_mb | number | No | Used space in MiB |
region_id | string | No | The region the volume lives in |
availability_zone | string | No | The availability zone within the region, where the vendor places volumes per zone |
instance_ids | string[] | No | Instances the volume is mounted on |
metadata | ComputeMetadata[] | No | Vendor labels, tags and metadata |
metadata[].id | string | No | |
metadata[].slug | string | No | The label, tag or metadata key |
metadata[].value | object | No | The label, tag or metadata value |
metadata[].namespace | string | No | The origin of the value (eg. labels, tags, metadata) |
metadata[].format | enum | No | The data type of the value Values: TEXT, NUMBER, DATE, BOOLEAN, ARRAY, OBJECT |
metadata[].extra_data | object | No |
Errors
Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).
{
"statusCode": 429,
"error": "Too Many Requests",
"message": "Too many requests to unified.to API; max requests per minute: N"
}| Status | Error | Meaning |
|---|---|---|
400 | Bad Request | The request was malformed or failed validation. |
401 | Unauthorized | The connection is likely broken; re-authorize it. |
403 | Forbidden | The connection is missing permissions or scopes. |
404 | Not Found | The requested resource does not exist. |
429 | Too Many Requests | Rate limit exceeded (see the two sources below). |
500 | Internal Server Error | An unexpected error occurred. |
501 | Not Implemented | Not supported by this integration. |
Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.
429 Too Many Requests
A 429 has two possible sources:
- The integration's own rate limit, passed through.
- Unified's workspace limit: a rolling 60 seconds, set by plan, with the message
Too many requests to unified.to API; max requests per minute: N.
const options = {
method: 'POST',
url: 'https://api.unified.to/compute/5de520f96e439b002043d8dc/volume',
headers: {
authorization: 'bearer .....'
},
data: undefined,
params: {
fields: '',
raw: '',
}
};
const results = await axios.request(options); Are we missing anything? Let us know