Makes a server in the team's Hetzner project and sets it up as a sandbox
server, the way Pyo makes a cluster's servers there. Read the locations,
server types and prices with getCloudOptions first. On its first boot it
joins your tailnet and runs sandbox.sh with a one-time code. Hetzner
Cloud servers have no KVM, so it runs sandboxes on gVisor. Follow it in
the server's cloud (creating, booting, joining, ready) and state.
Without confirm it answers 409 with the monthly price. Confirm that
with the user, then send it again with confirm: true. Team owners and
admins. Needs Tailscale and the team's Hetzner connection.
API key access: full.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
application/jsonteamId*stringThe team whose server it is: its cloud provider connection pays.
name*stringIts name in Pyo, on your tailnet and at the provider: lowercase letters, digits and dashes.
provider?|"hetzner" (the default).
location*stringA location's name from getCloudOptions ("fsn1").
serverType*stringA server type's name from getCloudOptions ("cx22").
edgeDomain?|A domain whose wildcard points at the server, as for
addSandboxServer.
sshKey?|Your OpenSSH public key, to sign in to it over your tailnet.
confirm?booleanWithout it the answer is 409 with the monthly price.
server (as listSandboxServers shows it) and cloudServer (id, name, state, monthly, currency).
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/sandbox-servers/cloud' \
-H 'Content-Type: application/json' \
-d '{
"teamId": "string",
"name": "string",
"location": "string",
"serverType": "string"
}'{}