Clean-room WebNIC integration modules for HostBill.
This repository contains three custom modules built outside core_dev/ and postman_webnic/:
webnic_domains- domain registrar modulewebnic_ssl- SSL provisioning modulewebnic_dns- DNS management module
Optional HostBill type assets for SSL are provided in:
webnic_types/class.webnicsslcert.php
- Keep implementation isolated from vendor/reference sources
- Rebuild WebNIC integration against HostBill module contracts
- Provide admin UI, DNS client UI, and module API endpoints
- Use
postman_webnic/Default module.openapi.jsonas the API contract reference
webnic_domains/
admin/
api/
class.webnic_domains.php
webnic_ssl/
admin/
api/
class.webnic_ssl.php
webnic_dns/
admin/
api/
templates/
user/
class.webnic_dns.php
webnic_types/
class.webnicsslcert.php
webnicsslcert/
core_dev/
postman_webnic/
Each module contains its own embedded WebNIC API client implementation to avoid runtime coupling between modules and to simplify HostBill deployment.
Embedded clients provide:
- JWT authentication
- automatic token reuse
- live and OTE environment switching
- JSON request helpers:
get,post,put,delete - binary download helper
- normalized error extraction
- Live:
https://api.webnic.cc/ - OTE:
https://oteapi.webnic.cc/
Token authentication uses:
POST /reseller/v2/api-user/token
HostBill domain registrar module for:
- domain registration
- renewal
- transfer-in
- deletion
- nameserver management
- registrar lock management
- WHOIS privacy management
- EPP/auth-code actions
- contact synchronization
- verification email resend
- ownership certificate download
Admin UI includes:
- domain snapshot panel
- registry/status panel
- contacts panel
- transfer status panel
- action panel for lock, unlock, EPP, sync, resend verify
Module API endpoints include:
snapshotactions
HostBill SSL module for:
- certificate order creation
- renewal
- reissue
- cancellation
- CSR validation compatible with HostBill SSL type flows
- dynamic CSR server/software list support
- DCV email lookup
- DCV method update
- DCV email resend / method change compatibility
- certificate synchronization
- certificate download
Admin UI includes:
- product-to-WebNIC product key mapping
- account certificate detail view
- CSR display
- DCV detail display
- change DCV workflow
- resend DCV email action
Module API endpoints include:
detailsdcv
HostBill DNS module for:
- zone creation
- zone deletion
- zone listing
- import zone listing
- reverse
.arpazone filtering - zone record listing
- add/edit/delete record
- nameserver summary
- supported record summary
- billing and zone-management visibility flags
UI includes:
- admin product config page
- admin app summary page
- DNS client controller integration
Module API endpoints include:
summaryzones
Copy these module folders into the appropriate HostBill module directories in your target installation.
Expected HostBill runtime mapping:
webnic_domains->includes/modules/Domain/webnic_domainswebnic_ssl->includes/modules/Hosting/webnic_sslwebnic_dns->includes/modules/Hosting/webnic_dns- optional
webnic_types/class.webnicsslcert.php->includes/types/class.webnicsslcert.php - optional
webnic_types/webnicsslcert/->includes/types/webnicsslcert/
Important: this repository is a development workspace. Final runtime placement must match your HostBill module loader expectations.
Configure in HostBill:
UsernamePasswordOTE EnvironmentRegistrant User IDDefault WHOIS PrivacyDefault Proxy
Configure server credentials:
- WebNIC API username
- WebNIC API password
- OTE environment flag
Configure product option:
product_key
Configure server credentials:
- WebNIC API username
- WebNIC API password
- OTE environment flag
Configure product options:
dns_templatemaxdomainns1..ns4hide_billinghide_zone_management
The following validation has been completed in this workspace:
- PHP syntax validation with
php -l - editor diagnostics check for touched PHP files
- Domain custom client-area controller was not added because a reliable HostBill reference pattern was not confirmed.
- SSL custom client-area controller was not added for the same reason.
- Final runtime behavior should be tested inside a real HostBill installation because controller discovery and template paths are environment-dependent.
- Some WebNIC response fields may vary by product/TLD/profile and may require final adjustment after integration testing.
- Deploy modules into a HostBill staging instance.
- Verify controller routing for admin, user, and api scopes.
- Test live actions against WebNIC OTE.
- Refine field mappings per TLD and SSL product.
- Add screenshots or internal runbooks if this repository will be handed to operations teams.
core_dev/for HostBill module patternspostman_webnic/Default module.openapi.jsonfor WebNIC endpoints and payload structures
- License:
GPL-3.0-or-later - Attribution:
Nguyen Thanh An by Pho Tue SoftWare Solutions JSC