Create a snapshot
POST/compute/{connection_id}/snapshot
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 snapshot
created_atdate-time
When the snapshot was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
When the snapshot was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
Display name of the snapshot
instance_idstring
The instance the snapshot was taken from
volume_idstring
The volume the snapshot was taken from
type enum
Valid values:
"MEMORY"
"DISK"
"OTHER"
Whether memory state is included
status enum
Valid values:
"CREATING"
"READY"
"FAILED"
"DELETING"
"OTHER"
Normalized snapshot status
size_mbnumber
Snapshot size in MiB
expires_atdate-time
When the snapshot will be deleted (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
Returns
| Response field | Type | Required | Description |
|---|---|---|---|
id | string | No | Unique identifier for the snapshot |
created_at | string (date-time) | No | When the snapshot was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
updated_at | string (date-time) | No | When the snapshot was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
name | string | No | Display name of the snapshot |
instance_id | string | No | The instance the snapshot was taken from |
volume_id | string | No | The volume the snapshot was taken from |
type | enum | No | Whether memory state is included Values: MEMORY, DISK, OTHER |
status | enum | No | Normalized snapshot status Values: CREATING, READY, FAILED, DELETING, OTHER |
size_mb | number | No | Snapshot size in MiB |
expires_at | string (date-time) | No | When the snapshot will be deleted (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
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/snapshot',
headers: {
authorization: 'bearer .....'
},
data: undefined,
params: {
fields: '',
raw: '',
}
};
const results = await axios.request(options); Are we missing anything? Let us know