Add a cluster whose first server Pyo makes at a cloud provider (team admins). It runs connect.sh there the way Add cluster's command does, over your tailnet. Without confirm it answers 409 with the monthly price. Confirm that with the user, then send it again with confirm: true.
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/jsonAdd a cluster whose first server Pyo makes at a cloud provider (team admins). It runs connect.sh there the way Add cluster's command does, over your tailnet. Without confirm it answers 409 with the monthly price. Confirm that with the user, then send it again with confirm: true.
API key access: full.
op*"createCloudCluster""createCloudCluster"id*stringA new id you choose: cl_ then 4 to 40 lowercase letters, digits, dashes or underscores.
teamId*stringname*stringThe cluster's name. Its first server is named <name>-1.
serverId*stringA new id you choose for its server: cs_ then 4 to 40 lowercase letters, digits, dashes or underscores.
provider?|"hetzner" (the default).
location*stringserverType*stringsshKey?string|nulltags?array<string>confirm?booleanDone. Always ok: true, and some operations add more, such as a new API key or a join command. A warning comes with a change that went through but won't fully take effect yet, such as more replicas than the servers have room for.
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/ops' \
-H 'Content-Type: application/json' \
-d '{
"id": "cl_8kq2x7ad",
"location": "Singapore, SG",
"name": "edge",
"op": "createCloudCluster",
"serverId": "srv_8kq2x7ad",
"serverType": "example",
"teamId": "team_8kq2x7ad"
}'{}