Skip to main content
POST
Resume failed default network provisioning
Requires no IAM action. Access is decided by the endpoint’s own rules rather than by a policy — see the description above.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

account_id
string<uuid>
required

Response

Current account onboarding

onboarding
object
required

Account-shared first-server progress. New accounts provision one IPv4 public subnet, an internet gateway, and a security group. No NAT gateway or public IP is allocated during setup. Existing accounts are never automatically provisioned.