I'm integrating domain registration into our platform using the Developer API, and I need to confirm a few specific points so I can build it correctly.
My goal is to let customers register domains across any TLD we offer — not just .com, but ccTLDs and others — fully through the API, with no hPanel step, including creating the WHOIS/contact profiles that registration references.
Could you confirm, precisely:
Is there a published Developer API endpoint to create a WHOIS/contact profile (returning the profile/contact IDs used for owner, admin, billing and technical roles)? Please give the exact method and path.
Does that profile-creation endpoint support the varying registrant requirements of different TLDs? Some TLDs require extra fields or registrant data beyond the standard set (for example local-presence details, ID/registration numbers, or country-specific fields). Can these all be supplied via the API when creating the profile, or do some TLDs require hPanel to complete the contact/registrant data?
Once a valid profile exists and is referenced in the registration request, does a card-paid order complete registration automatically — moving from pending_setup to active with no further action — or is a separate finalisation step always required?
If a paid order lands in pending_setup, is there a published API endpoint to finalise that existing order (reusing the same subscription/resource, not a new purchase)? If yes, please give the exact method and path. If no such endpoint exists, please state plainly that finalising a pending_setup domain currently requires hPanel.
Are there any TLDs where end-to-end API registration is not possible and hPanel is always required? If so, which categories?
For context, I've already confirmed on my account that availability checks work, the registration request is accepted, payment succeeds, and the domain then sits in pending_setup. So my core open question is what completes registration from that point via the API, and whether that behaviour is consistent across all TLDs or varies by TLD.
I'm not looking for any undocumented or unsupported workaround — I need to know definitively whether the end-to-end flow (profile creation → registration → active) is achievable through the published API today for the full range of TLDs, or whether specific steps or specific TLDs currently require hPanel.
I'm integrating domain registration into our platform using the Developer API, and I need to confirm a few specific points so I can build it correctly.
My goal is to let customers register domains across any TLD we offer — not just .com, but ccTLDs and others — fully through the API, with no hPanel step, including creating the WHOIS/contact profiles that registration references.
Could you confirm, precisely:
Is there a published Developer API endpoint to create a WHOIS/contact profile (returning the profile/contact IDs used for owner, admin, billing and technical roles)? Please give the exact method and path.
Does that profile-creation endpoint support the varying registrant requirements of different TLDs? Some TLDs require extra fields or registrant data beyond the standard set (for example local-presence details, ID/registration numbers, or country-specific fields). Can these all be supplied via the API when creating the profile, or do some TLDs require hPanel to complete the contact/registrant data?
Once a valid profile exists and is referenced in the registration request, does a card-paid order complete registration automatically — moving from pending_setup to active with no further action — or is a separate finalisation step always required?
If a paid order lands in pending_setup, is there a published API endpoint to finalise that existing order (reusing the same subscription/resource, not a new purchase)? If yes, please give the exact method and path. If no such endpoint exists, please state plainly that finalising a pending_setup domain currently requires hPanel.
Are there any TLDs where end-to-end API registration is not possible and hPanel is always required? If so, which categories?
For context, I've already confirmed on my account that availability checks work, the registration request is accepted, payment succeeds, and the domain then sits in pending_setup. So my core open question is what completes registration from that point via the API, and whether that behaviour is consistent across all TLDs or varies by TLD.
I'm not looking for any undocumented or unsupported workaround — I need to know definitively whether the end-to-end flow (profile creation → registration → active) is achievable through the published API today for the full range of TLDs, or whether specific steps or specific TLDs currently require hPanel.