Provider guides
Pterodactyl: configuration and operations
Provision game servers on a Pterodactyl panel from paid service products.
On this page
Provider workflow
Provision game servers on a Pterodactyl panel from paid service products. The adapter maps each Agovena instance to a panel server, checks deployment resources and supports suspension, reactivation, termination, plan changes and status synchronization. Customer power actions additionally require a Client API key.
Requirements
Agovena Core ^0.0.1. Enable Provisioning before this extension.
This extension is not marked production-ready. Validate its supported workflow in your own test environment before accepting customer orders.
Set up the package
Enable Provisioning and the Pterodactyl extension with their migrations. Create a server connection using panel_url, secret application_api_key and user_id. Add secret client_api_key only when customer power actions are required. Keep verify_tls true. On the product, configure location_id, nest_id and egg_id, then set resource limits and egg environment overrides.
Provider-specific boundaries
Use a panel root such as https://panel.example.com, not a URL containing credentials or an API path. The Application API key manages server resources; the optional Client API key powers an existing customer server. These keys are not interchangeable. The required user_id is the panel owner of the created server, not the Agovena customer ID.
Product fields include location_id, nest_id, egg_id, memory, swap, disk, io, cpu, databases, allocations, backups, docker_image, startup, secret environment and dedicated_ip. Environment overrides are newline-separated KEY=value entries; use placeholders in shared examples and keep actual values in protected settings. Empty image and startup overrides use the egg values.
Test a paid service through creation, installation, ready state, suspension and reactivation. Check limits and ownership on the panel itself. Then test termination only on a disposable instance. A malformed mapping, missing allocation or mismatched owner must be investigated, not bypassed by editing a remote ID. A stopped process is not the same as a suspended hosting service. Keep queue and polling workers running so long operations can be reconciled. 2
Configuration contract
| Field | Type | Required | Secret | Default |
|---|---|---|---|---|
panel_url |
string |
Yes | No | Empty |
application_api_key |
string |
Yes | Yes | Empty |
client_api_key |
string |
No | Yes | Empty |
user_id |
string |
Yes | No | Empty |
verify_tls |
boolean |
No | No | true |
timeout |
string |
No | No | "15" |
These are the declared manifest fields. A field marked optional may still be required by an API operation, as described above. Store secret values only in protected settings, never in product descriptions, URLs or shared examples. 1
Operation and failure handling
The adapter checks ownership and configuration before using a stored mapping. Existing servers can be recovered by the stable agovena-{instanceId} external ID instead of blindly creating another server. Installing and restoring states remain provisioning, installation failure becomes failed and unfamiliar lifecycle data requires manual review. Power actions are limited to start, stop and restart and are unavailable without a Client API key.