---
title: "Resize a VPS"
method: POST
path: "/services/{id}/resize"
tags: ["Services"]
---

# Resize a VPS

`POST /services/{id}/resize`

## Request

- Base URL: `https://api.imprezahost.com/v1`
- URL: `https://api.imprezahost.com/v1/services/{id}/resize`
- Auth: API key in header `X-API-Key` and API key in header `X-API-Secret`

Gives a configurable VPS more vCPUs, memory or disk. Sizes only go up; the location, the
operating system and the billing cycle stay as they are. Priced by the billing system
(pro-rated to the next due date), paid from the account balance, which must already
cover it, and written to the VPS once paid. The new vCPU count and memory reach the
running system after a restart through the API (a reboot from inside the server keeps
the old ones); the disk is enlarged at once. A retry of a resize
that went through answers `409 NO_CHANGE` and charges nothing. Requires the `manage`
scope.

## Path parameters

- `id` integer, required

## Request body

- object
  - `cpu_cores` integer
  - `memory_gb` integer
  - `disk_gb` integer
  - `max_amount` string: Optional. The resize is refused with `PRICE_ABOVE_LIMIT` if it would cost more.

## Response `201`

Resized and paid

## Other responses

- `400`: As for the quote
- `402`: `PAYMENT_NOT_SETTLED` — the balance changed while the resize was placed; it was withdrawn and nothing was charged
- `404`: No such VPS on this account
- `409`: `NO_CHANGE`, `SERVICE_NOT_ACTIVE`, `UPGRADE_IN_PROGRESS`, `INSUFFICIENT_BALANCE` (with `top_up_needed`), `PRICE_ABOVE_LIMIT` or `ORDER_IN_PROGRESS`

---

[API](https://skmtc.dev/imprezahost/apis/impreza-host-public-api.md) · [All operations](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/revisions/db86511f604f?raw)