Skip to content

Request a higher Cloud VPS limit

POST /api/v2/vps/payg/limits/requests

Asks Hostup to raise one Cloud VPS limit, such as CPU cores or the number of Cloud VPS. Name the limit in limitType and the new value in requestedLimit. To move a fixed-term VPS to a bigger plan, use POST /api/v2/vps/{id}/actions/upgrade instead. Only one request per limit type can wait at a time. A second one returns 400. That answer has the general detail “The request is invalid.” and no errors[].pointer. The same 400 comes back when requestedLimit is not higher than currentLimit. Check pendingRequests on GET /api/v2/vps/payg/limits first. The call returns 403 when Cloud VPS access is not turned on for the account.

The limit stays the same until Hostup approves the request. When Hostup decides, the request leaves pendingRequests and the account holder gets an e-mail with the decision. An approved request shows as the new value in max.

Authentication: An API key with the scope write:billing. About keys and scopes

Request

Body

limitTypestringrequired
Which limit to raise. cpuCores, memoryGb and storageGb are CPU cores, memory in GB and disk in GB. vmCount is the number of Cloud VPS. floatingIpCount, snapshotCount and privateNetworkCount count those items. mailRelayEmails is mail relay e-mails per month. One of cpuCores, memoryGb, storageGb, floatingIpCount, vmCount, snapshotCount, privateNetworkCount, mailRelayEmails.
currentLimitinteger
The limit today, from max on GET /api/v2/vps/payg/limits. requestedLimit must be higher. Default 0. At least 0.
requestedLimitinteger
The new limit, a whole number above 0. For mailRelayEmails, a multiple of 1,000. Required unless requestedMax carries the value. At least 1.
requestedMaxobject
Another way to send the new value: an object keyed by limit type. Only the entry for limitType is used.
cpuCoresinteger
memoryGbinteger
storageGbinteger
floatingIpCountinteger
vmCountinteger
snapshotCountinteger
privateNetworkCountinteger
mailRelayEmailsinteger
reasonstringrequired
Why you need the higher limit. At least 10 characters.
useCaseDescriptionstring
More detail about the workload. It is stored with the reason.

Example

POST /api/v2/vps/payg/limits/requests
curl -X POST "https://cloud.hostup.se/api/v2/vps/payg/limits/requests" \
-H "Authorization: Bearer $HOSTUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"limitType": "cpuCores",
"currentLimit": 16,
"requestedLimit": 32,
"reason": "More traffic expected after a product launch."
}'

Responses

200 The request was sent for review.

Response 200
{
"id": "payglim_01hxa3b4c5d6e7f8g9h0j1k2m3",
"status": "submitted"
}
Response fields
idstring or null
ID of the request (payglim_…). It is listed in pendingRequests while it waits.
statusstring
Always submitted. One of submitted.

Errors

Errors are Problem Details with a stable code. Branch on the code, not on the text.

400The body is invalid: an unknown field, a limitType that is not listed, a requestedLimit that is not a whole number above 0 or not a multiple of 1,000 for mailRelayEmails, or a reason under 10 characters. errors[].pointer names the field, for example /reason. Two cases return the detail “The request is invalid.” without errors: requestedLimit is not above currentLimit, or a request for this limit type is still waiting. Check max and pendingRequests on GET /api/v2/vps/payg/limits first.
401Unauthorized. Authentication is required.
403Cloud VPS access is not turned on for the account. detail does not say so. access.blockerReasons on GET /api/v2/vps/payg/deployments shows what is missing. A key without the scope also gets 403, with requiredScopes.
404Not found. The resource does not exist or is not owned by the caller.
429Rate limited. Retry after the limit resets. 429 responses include Retry-After seconds plus X-RateLimit-* headers.
500Internal error. Retry later or contact support if the issue persists.