Module and release scope
This guide covers CentralNic Reseller 1.0.0, Extension API 1, from the reviewed product source. Its declared core range is 1.3.6–1.3.99. Use the matching released core and signed provider package; a version label alone does not install the required contracts. Source availability does not mean the module is bundled in every currently downloadable product, installed on your server, enabled or certified for your merchant/server account. Nothing in this guide enables a provider or changes your existing connections.
Open System → Domain registrars (newer source may group these as Payments, Domain services or Hosting services). Install the reviewed signed package through Modules & addons or the integration workspace's Install tab, enable the module separately, add an account/connection, save its own credentials, run its stated Test and explicitly enable the connection. Saving or retesting disables the connection until you enable it again. Start with the provider's test environment where supported; otherwise use an isolated account or server.
Exact connection fields
These are the fields declared by this module. Secret values are entered privately and encrypted by the application. Defaults are configuration hints, not approved live merchant settings. Internal fields are populated by the module and are not operator-editable.
| Key / label | Type | Required | Default / guidance |
|---|---|---|---|
environment — Environment |
select | Yes | Default: "sandbox" Choices: sandbox = OT&E, live = Live |
username — API login |
text | Yes | Use the account-specific value described below. |
password — API password |
secret | Yes | Use the account-specific value described below. |
allow_writes — Allow domain purchases and changes |
boolean | No | Default: false |
allow_automated_renewals — Allow paid-invoice automated renewals |
boolean | No | Default: false |
Registrar API module for CentralNic Reseller (RRPproxy). Install leaves the module disabled; it creates no accounts and changes no settings. Existing HEXONET accounts must use the API account/platform to which CentralNic has migrated them; this package does not assume legacy HEXONET credentials work on CentralNic.
Configure
- Obtain a funded reseller account and create an API user. Allowlist the application's outbound server IP where required. Match OT&E credentials to OT&E and production credentials to production.
- Enable this module, create a registrar connection, select OT&E, enter API login/password, and run Test. Test only reads account identity/currency.
- Run your own OT&E registration, renewal, transfer and domain synchronization acceptance checks with permitted test domains before switching credentials/environment to live.
- Enable Allow domain purchases and changes only when ready. Automated paid-invoice renewals need the separate permission. Both write permissions default off.
The module uses fixed HTTPS REST endpoints https://rest-ote.rrpproxy.net/v1 and https://rest.rrpproxy.net/v1, HTTP Basic authentication, bounded responses and a single request per submission. No webhook URL is required. API approval, funding and IP rules are controlled by CentralNic.
Supported operations
Availability, registration, transfer-in, explicit renewal, synchronization, nameservers, transfer lock/unlock, and existing authorization-code retrieval. Transfers remain pending until completed. Renewal requires a fresh expiry check and a later expiry after submission. A successful HTTP reply alone never confirms a renewal. Registry-specific requirements, premium fees, trustee purchases, trades, restoration and destructive deletion require the provider panel; this version does not silently accept additional charges.
Registration creates a contact from the owning customer's profile (including international phone), then sends that handle for all contact roles and the selected nameservers. An existing customer-owned registrant_handle such as P-... can be supplied in advanced provider options. It must resolve in the selected reseller account; do not use a reseller/business contact for an unrelated customer. Domain synchronization with an expected customer contact also reads the linked contact and checks its details. Unexpected registrant or nameservers keep activation pending for review.
An order accepted by the registrar may still require registry/contact verification. Synchronize instead of resubmitting a purchase when a timeout or pending result is shown. API error text and status codes appear in diagnostics with credentials/contact data removed. No pricing import is provided; use the product's catalogue prices.
Official references:
- Current REST integration guide
- Authoritative OT&E OpenAPI schema
- Transfer requirements
- Renewal command and TLD restrictions
Incoming transfers preserve the domain’s existing delegation. The core must confirm the current public nameservers (or an administrator must supply the confirmed current set) before submitting a transfer; this module never invents reseller nameservers during transfer.