Skip to main content
PATCH
Reduce capacity
Gives back computers the account added before 2026-10-27, when buying capacity still added computers. Send how many of those added computers to keep. The current period is already paid for, so the computers, the memory, vCPU and disk they came with, and the bill stay until the next renewal, then drop together. Sending the current number undoes a pending reduction.
Memory, vCPU and storage bought since 2026-10-27, by size or by amount with Add capacity, can’t be given back here. Lower them on Plan & billing with the RAM, vCPU and storage add-ons. That also takes effect at the next renewal.
added.computers in Get capacity counts the computers added before 2026-10-27. Only those on a monthly term can be given back. A yearly term runs to its end. An account that added none has nothing to give back: sending 0 answers scheduled: null, and a higher number answers 400 with That is more than this account has added. Capacity a running computer stands on can’t be given back: the answer is 409 with code in_use, and either min_added_computers (how many added computers are in use) or part (ram, vcpu or disk, the part running computers use). Shrink or delete computers first, or keep more. Over a rate limit, the answer is 429 with code rate_limited and a Retry-After header. This endpoint allows 20 changes a minute, together with Add capacity, and every call also counts toward your plan’s limit for other API calls. See Account limits and rate limits.

Authorizations

Authorization
string
header
required

API key authentication. Get your key at orgo.ai/workspaces

Body

application/json
added_computers
integer
required

How many of the computers added before 2026-10-27 to keep. Only those on a monthly term can be given back.

Required range: x >= 0

Response

The scheduled reduction and the account's capacity.

scheduled
object | null
capacity
object