Rent a dedicated server
POST/dedicated/rentals
Supply exactly one format: disk_layout for a shared-layout plan, or disk_layouts for a disk-group plan. disk_layouts maps the catalog disks[].id values to supported layout codes for those groups. Include every group and no extra keys. IDs are opaque: do not derive them from disk types. The client selects defaults; the API does not fill them in. Preserve the selection when retrying an order.
Choose plan_id from the dedicated catalog. The platform chooses the physical server. Supply exactly one password or SSH public key, also for quotes. extra_ipv4_count adds addresses to this rental at a fixed price. A completed purchase order confirms reservation; wait for dedicated.issued / rental status active before handing the server to your customer. The term starts when issued.
Send a unique Idempotency-Key for each intended action. If the response is lost, retry with the same key and unchanged parameters; do not create a new key for the same purchase.
HTTP 202 accepts the request; it does not confirm completion. Save the order_id or operation id and check its status.
HDD groups support RAID 5 (at least 3 disks), RAID 6 (at least 4) and RAID 10 (an even number of at least 4), when listed among the group options. These options are unavailable for other disk types and shared layouts.
Request rules and errors · Lifecycle · Webhooks
Request
Responses
- 202
- 401
- 403
- 404
- 409
- 422
- 500
- 503
Accepted for processing
Missing or invalid key, mismatched ID, or inactive integration
Client IP is not in the integration allowlist (ip_not_allowed).
Resource not found in this integration
Business or state conflict; inspect detail
Invalid request fields or unsupported parameters
Unexpected server error
Service unavailable or result unconfirmed; for a mutation retain its idempotency key