Delete a server Pyo made at a cloud provider (team admins): its services move off it, it leaves the cluster and your tailnet, then it's deleted at the provider. Only servers with this installation's label are ever deleted there. A cluster's first server goes once the cluster is removed. Without confirm it answers 409 with the monthly cost that stops. 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/jsonDelete a server Pyo made at a cloud provider (team admins): its services move off it, it leaves the cluster and your tailnet, then it's deleted at the provider. Only servers with this installation's label are ever deleted there. A cluster's first server goes once the cluster is removed. Without confirm it answers 409 with the monthly cost that stops. Confirm that with the user, then send it again with confirm: true.
API key access: full.
op*"deleteCloudServer""deleteCloudServer"id*stringThe cloud server's id (cs_…), from cloudServers in getState.
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 '{
"confirm": true,
"id": "cs_8kq2x7ad",
"op": "deleteCloudServer"
}'{}