Account Creation Hooks
Use Eenos createacct pre/post hooks with prepared account data, CREATE actions and the actual provisioning sequence.
| Property | Value |
|---|---|
| Function/directory | createacct |
| Pre scripts | /var/eenos/hooks/createacct/pre/ |
| Post scripts | /var/eenos/hooks/createacct/post/ |
| Delivered actions | CREATE |
| Panel label | wap |
The shared account provisioning routine emits createacct hooks with panel=wap and action=CREATE. The panel value is a literal from this backend path; it is not proof that an operator clicked the WAP interface. API or reseller provisioning that reaches the shared routine can receive the same label.
Payload and timing
data is the prepared hosting-account mapping: user/domain, contact email, owner, package-derived limits, home, shell, network, reseller and other configured account fields. It is not the HTTP createacct request body, and it is not a promised plaintext password delivery channel. Fields depend on the account configuration.
The pre-hook runs after account configuration files have been written and before the operating-system user and account services are configured. It is therefore not a before-any-write validator. The post-hook runs after those provisioning steps reach the success branch. DNS CREATE hooks are separate calls within account service configuration; avoid performing duplicate work in both integrations.
Use and limitations
Use the post-hook for an idempotent follow-up notification or reconciliation task. Key your integration by account/domain and avoid assuming exactly-once delivery. A nonzero hook exit does not reject account creation or request a rollback. Changing the decoded dictionary in your script cannot modify the parent operation: it is a serialized copy in a separate process. Use the supported account operation or configuration workflow for actual account changes.
Script contract
Each script receives command-line key=value arguments: base64-encoded JSON data, uppercase action, lowercase panel and optional domain/user. Use the argument decoder examples and installation guide. Scripts run in lexicographic filename order within each phase. There is no automatic retry, hook-specific timeout or parent-operation veto from a nonzero exit code.