Module and release scope
This guide covers INWX 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 — INWX username |
text | Yes | Use the account-specific value described below. |
password — API password |
secret | Yes | Use the account-specific value described below. |
totp_secret — Two-factor shared secret (if required) |
secret | No | Use an API-specific account when possible. Keep this optional secret encrypted. |
allow_writes — Allow domain purchases and changes |
boolean | No | Default: false |
allow_automated_renewals — Allow paid-invoice automated renewals |
boolean | No | Default: false |
INWX DomRobot registrar module. It installs disabled and includes no credentials or customer data. Remote-write and automated-renewal permissions both default off.
Configure
- Create an INWX API-enabled account, fund it and apply the provider's API access/IP restrictions. Register a separate OT&E account; production credentials do not work in OT&E.
- Enable the module and create a registrar connection with OT&E, username and password. If the API account requires two-factor authentication, save its Base32 shared secret in the optional encrypted field. Test logs in/unlocks and logs out; it never changes a domain.
- Validate the full registration, transfer, renewal and synchronization flow using permitted test domains before switching the environment/credentials to live. Enable domain writes explicitly; automated paid-invoice renewals require a separate permission.
Fixed JSON-RPC endpoints: https://api.ote.domrobot.com/jsonrpc/ and https://api.domrobot.com/jsonrpc/. Sessions use memory-only cookies and are not persisted between operations. A single operation logs in, executes the necessary commands, then logs out. No webhook is needed. Credentials, cookies, contact details and authorization codes are redacted from provider errors.
Supported operations
Availability, registration, transfer-in, explicit renewal, synchronization, nameservers, transfer lock/unlock, and existing EPP code retrieval where the registry provides it. A registration creates the owning customer's contact with contact.create and uses it for all roles. Advanced provider option registrant_id can select an existing customer-owned numeric contact ID, verified with contact.info; it must not be another customer's or the reseller's default contact.
Registration sends an explicit nY period and chosen nameservers. Transfer includes the supplied authorization code and nameservers. Both remain pending after acceptance until synchronization. Domain reads require exact domain identity, owned repository ID, known state and a valid expiry. When the application supplies expected registrant/DNS details, the returned registrant is compared and mismatches remain pending. Renewal sends the fresh current expiration date and is only confirmed after expiry advances. Registrar auto-renew is off on new orders to leave billing renewal under application control.
TLD-specific eligibility, premium purchases, trustees, contact ownership trades, restoration and deletion are handled through the INWX panel in this version. Registry-generated auth codes may need a separate assisted request for some country-code TLDs. No pricing import is provided. Pending or timed-out submissions must be synchronized/reviewed before resubmission; no automatic retries occur.
Official references:
- INWX API overview and test system
- DomRobot API documentation
- Official client authentication/session and JSON-RPC protocol
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.
INWX may return an ok domain together with separate domain flags, a no-delegation flag or pending/failed registrant-verification status. Explicit hold, pending, failed verification and missing delegation keep activation pending even when contact and nameservers otherwise match. Omitted optional flags do not create an invented restriction.