The HostBill connector maps standard domain contact and nameserver data into current Domain Nexus requests. Verify the data needed for your selected TLD before accepting an order, especially when a registry requires organisation identifiers or other additional attributes.
IN THIS ARTICLE
01 Prepare standard registration data
- Confirm the intended end-customer registrant and accurate name, organisation, address, country, phone and email information.
- Review the per-role contacts supplied by HostBill. The connector uses the available registrant, administrative, technical and billing roles, with the customer as registrant when that is the available native source.
- Configure the intended nameservers and verify that they already serve the required DNS zone.
- For a transfer, enter the current authorisation code through the appropriate protected HostBill field.
- Check the current TLD requirements in Domain Nexus and validate the proposed data before committing a paid operation.
02 Recognise the extra-field boundary
The supplied HostBill registration and transfer method builds its request from domain, years, standard contacts, nameservers and the transfer code. It does not forward an arbitrary HostBill custom-field collection as additional_fields.
For a TLD requiring data outside that mapping, arrange the supported upstream or manual review workflow, or a separately reviewed connector extension. Adding a field to a HostBill order form does not by itself prove the value reaches the registry.
Test the real selected TLD and contact type in the installed HostBill version. Keep error codes and field names while avoiding unnecessary copies of identity documents. Do not insert made-up values simply because a local form requires a string.
Common questions
Can I sell a restricted TLD through the default form?
Only when all required data and review steps are covered by the actual integration. Confirm this before publishing an automated checkout for that extension.
Does a successful connection test validate contacts?
No. It reads the authenticated reseller profile. Registration data is checked in the relevant domain workflow.
Will changing the HostBill customer's profile update every registered domain?
Do not assume it does. Use the domain's contact update operation and verify its provider result. Billing profile data and registered-domain contacts are separate.
What should I provide when a field is rejected?
Send the TLD, field identifier, validation error and redacted request reference. State whether the field came from a native contact object or a custom form so support can identify the mapping boundary.