The supplied Domain Nexus release includes generated connectors for WHMCS, HostBill, Blesta and FOSSBilling. It does not include a native WiseCP connector. A WiseCP integration therefore needs its own reviewed registrar module using the current Domain Nexus API.
IN THIS ARTICLE
01 Define the integration before development
- Check the installed WiseCP release and its current registrar-module interface.
- Map the required customer workflows: availability, registration, transfer, renewal, domain details, nameservers, contacts, lock and authorisation-code handling.
- Record the current API endpoint and permitted authentication method. For our reseller API, the base is
https://my.nabtech.co/modules/addons/nabtechresellerdns/api/index.php. - Define how local customer, order and invoice references map to owned domains and durable API operations.
- Decide which optional DNS, privacy, forwarding and registry-specific fields can be implemented accurately in the native interface.
02 Build the important boundaries
Use WiseCP's documented registrar-module structure and callbacks. Keep API credentials on the server and retain TLS verification. Implement current v2 authentication; do not reuse the retired DomainsReseller hourly-token protocol.
Persist idempotency keys and original request inputs for paid operations. A queued response must remain pending locally until the upstream result is confirmed. Domain sync should use confirmed registration status and expiry without creating a new purchase.
Read current TLD requirements and prices before order submission. Do not infer transfer eligibility from an availability response alone, or make an optional feature visible without its account and provider checks.
Common questions
Can I install the WHMCS ZIP in WiseCP?
No. Billing platforms have different module contracts and discovery paths. A package for another platform is not a native WiseCP integration.
Does WiseCP's Generic EPP module connect to this REST API?
EPP and this HTTPS JSON API are different interfaces. Use a purpose-built integration for the documented current API rather than assuming protocol compatibility.
What counts as a completed integration?
Verify installation, account scoping, native order forms, registry fields, pricing, pending-operation recovery, cron sync and customer permissions on the intended WiseCP version. A successful profile call is only the initial connection check.
How should deployment be staged?
Retain a working previous version, use a controlled environment and enable only verified TLDs and features. Publish clear customer instructions for any task that remains in the reseller portal.
Related articles
- Can I resell Nabtech domains without WHMCS?
- Migrate an integration from the retired DomainsReseller API to Domain Nexus v2
- Retry Domain Nexus requests without creating duplicate domain operations
- Build domain forms from current registry field and consent requirements
- Plan a FOSSBilling connector test without assuming a live sandbox exists