Developer
Server Client API
Updated steps and current-interface reference for server client api.
Current endpoint
The game panel uses the Pterodactyl Client API at https://panel.caforahost.com/api/client. The older api.caforahost.com/v1 examples are not the public API verified for this deployment.
| Method and path | Purpose |
|---|---|
GET /api/client | Servers accessible to the account |
GET /api/client/servers/{identifier} | Server details |
GET /api/client/servers/{identifier}/resources | Runtime state and resources |
POST /api/client/servers/{identifier}/power | Power action, JSON signal |
POST /api/client/servers/{identifier}/command | Console command, JSON command |
Use a Panel Client API key with Authorization: Bearer ... and Accept: application/json. Keep keys out of public documents and frontend bundles. The identifier belongs to your server, not a Store order.
curl --fail-with-body \
-H "Authorization: Bearer ${PANEL_API_KEY}" \
-H "Accept: application/json" \
"https://panel.caforahost.com/api/client/servers/${SERVER_IDENTIFIER}/resources"Set the variables privately first. The resource response exposes runtime state as attributes.current_state; it does not provide a reliable player list. Writes have real effects, so test them on your own test service.