Skip to content
NimbusNexus

Region requests

By default new accounts get access to one region (whichever they picked at signup). Adding access to additional regions requires a region request — a short form explaining the workload that needs the new region. Most production accounts are approved within a business day; the gating exists for capacity planning and to flag unusual patterns (a brand-new account asking for capacity in five regions on day one is worth a brief conversation).

This endpoint also handles quota uplifts — a request to raise the VM count, vCPU, or storage limit in a region you already have access to. Same gating reason: large requests need capacity planning. See Quotas for the quota model itself.

The API surface here exists so programmatic deployment can fire-and-forget the request; the approval still happens manually on our side (this is one of the few corners of the API that isn't fully self-service by design).

What's next

  • Regions — the list of available regions.
  • Quotas — the per-project limits a region-request can also adjust.
  • Account overview — the account context for region access.

Reference

POST/api/v1/account/region-requests

Submit Region Request

Records a region request. Idempotent in spirit — duplicate submissions from the same email + region are accepted as separate rows so analytics can see the strength of demand over time. Rate limiting on the proxy side keeps this from being abused. Originating IP is captured for fraud forensics; auto-purged after 365 days by the retention job.

Request body

JSON body required.

Responses

  • 200Successful Response
  • 400Bad Request
  • 422Validation error
  • 500Internal Server Error

https://api.nimbusnexus.net/api/v1/account/region-requests

Need to make a real call? Try these endpoints in the live Swagger UI →