An application connection stores the details HostBill uses to reach a provisioning server or provider. Create and test the connection before assigning it to a sellable product. The fields and available actions depend on the activated module.
IN THIS ARTICLE
01 Add the connection
- Confirm that the required provisioning module is available in your licence and activated for the installed HostBill version. Follow its vendor instructions for the provider-side account, token and permissions.
- Open Settings > Apps Connections. Select the relevant module and use Add new connection.
- Give the connection a clear operational name that distinguishes production, test and location. Enter the module-specific hostname, endpoint and authentication details. Use a trusted encrypted connection where the integration supports it.
- Save and run Test configuration. If it fails, check the provider endpoint, certificate, credentials and source-IP restrictions. Do not assume a successful login through your browser establishes API connectivity from HostBill.
- Review Auto-provisioning availability. Disable automatic selection for a connection intended only for internal testing. Check the default connection when more than one exists.
- Open the intended product's Connect with App tab and select the module and appropriate connection. Complete the module-specific package mapping before testing a controlled order.
02 Verify the resulting service
Confirm that the test service was created on the intended provider account with the correct package, limits and customer ownership. Check a supported lifecycle action such as suspension and recovery in a disposable test account. A connection test verifies reachability, not the full commercial service configuration.
Common questions
Why is a module missing from the product's selection list?
The product list shows activated modules. Check module installation, activation, compatibility and the selected order type before changing the product itself.
Can every product use multiple server connections?
No. Some simple hosting modules support distributing new accounts across selected connections. Products whose resources depend on server-specific IDs need a module-specific design; do not assume those IDs are interchangeable between servers.