The audited build includes WHMCS, HostBill, Blesta and FOSSBilling connector templates. Each platform has a different installation path and credential workflow. Do not label another platform as supported simply because it can make HTTP requests.

1. Open Domain Reseller > Connector Studio.
2. Create a draft with the intended platform, stable module slug, display name and version.
3. Complete branding, documentation and support details. Use your legitimate company assets and final HTTPS API endpoint.
4. Select the permitted audience: the platform operator can target all eligible resellers, a group or one account; a master publisher is restricted to its downstream recipients.
5. Save, then build the draft and inspect its result and release details.

A generated package must be installed and tested on the intended billing platform. Verify discovery, authentication, TLD assignment, prices, scheduled synchronization and a representative domain operation. A successful ZIP build does not demonstrate the behaviour of every licensed host installation.

The downloadable package should not contain reusable reseller credentials. Recipients configure their own permitted API identity using the platform-specific guide. Check generated documentation and support links as well as the PHP module.

Use the current publication workflow and its confirmation. Published releases are immutable: withdraw a release before editing it, or create a new version for an update. Do not rebuild a published version in place while customers may be downloading it.

Check the recipient's Module downloads page to confirm the release appears only for the intended audience. Download grants are controlled and should not be treated as unrestricted public links.

No. Withdrawal stops future eligible downloads and invalidates outstanding grants. Customers who already installed that package need a coordinated update or retirement process.

Document version changes, minimum platform expectations and any required configuration migration. Keep the module slug stable across routine updates so the host recognises the existing connector and saved settings.

If a build or publication fails, read its specific error. A busy build, duplicate release identity, invalid audience and missing permission are separate problems. Avoid using older build endpoints to bypass the current catalogue workflow.

For an urgent defective release, withdraw it and publish a corrected version with clear update instructions. Credential rotation remains a separate account action.

• Install the current Nabtech Domain Nexus registrar connector in WHMCS
• Install the current Nabtech Domain Nexus connector in HostBill
• Connect Blesta Domain Manager to us Domain Nexus
• Install the Nabtech Domain Nexus registrar adapter in FOSSBilling
• Grant master-reseller access and define downstream responsibilities