OnlineNIC V4

Connect an OnlineNIC reseller account through its HTTPS domain API and manage eligible domain services in WISECP.

Accessing the Screen

Open Products → Domain Names → Domain Registrars → All Modules → OnlineNIC V4: {admin}/module/registrars?module=OnlineNICv4.

What Is on the Screen?

The form contains connection settings, default nameservers, connection testing and saving. Domain import, extension import and automatic cost updates are unavailable.

Prepare the Provider Account

Activate reseller access and request domain API credentials. OnlineNIC lists downloadable documentation under API/Template → API in its reseller panel. Confirm API-key access and the server's outgoing IP allowlist with OnlineNIC. Consult the official API reference. This module uses HTTPS JSON at api.onlinenic.com; OTE uses ote.onlinenic.com on port 5999. Allow these outbound connections, enable PHP cURL and intl, and keep the server clock accurate.

Settings

Available Actions

Connect and Check

1. On the OnlineNIC V4 form, enter the three credentials and select Test Mode only for OTE credentials.
2. Click Test Connection. It checks example.com availability; success does not prove sufficient funds or permission for every operation.
3. Click Save Changes, reopen the form and check the settings. A separate WISECP server record is unnecessary.

Prepare Extensions and Prices

Under Products → Domain Names, follow the Domain Extensions guide to assign OnlineNICv4. Enter registration, renewal and transfer prices manually, checking periods and currency against the provider. There is no catalogue or price feed. A provider-supported extension may still require capabilities absent from this module.

Existing account domains cannot be listed for import. Use the Registrar Configuration guide for service mapping. Keep a trial extension inactive, then check a controlled OTE domain before opening sales. An inactive sales extension does not prevent charges from a live manual order.

Manage a Domain

Open the domain under Orders → Services. Registration, incoming transfer, renewal, nameserver changes, WHOIS contacts, transfer lock and authorization-code retrieval are available. Restore, DNS records, DNSSEC, URL forwarding and email forwarding are unavailable; leave dependent customer options disabled.

Registration sends up to four nameservers and four contact roles. For .us, check Application Purpose and Nexus Category; .uk requires Legal Type and Business License. Confirm registry eligibility before ordering. A transfer may need the current authorization code; an empty or N/A response does not supply one.

In the service's WHOIS section, updates can change shared provider contacts and affect other domains. A partial failure can leave some roles updated. Child nameservers can be added, changed and deleted. Their list comes from saved service data, not a complete provider inventory. Renaming deletes the old host before creating its replacement; check dependent domains and preserve its addresses first.

WHOIS privacy uses ID Shield. Purchasing its addon requests one year with automatic renewal disabled. Enabling or disabling resumes or suspends existing protection; cancellation suspends it and does not establish a refund. Customer controls also depend on service options, addons and permissions.

Check Synchronization

Scheduled synchronization reads dates and status. Compare them with the provider after a controlled test. A failed information request can also fail synchronization; it does not prove the domain has disappeared. Confirm the provider's order result before retrying registration or transfer.

Important Notes

Required Permissions

Configuration requires Domain Registrars permission. Domain operations require the appropriate administrator or customer permissions and provider access.

Related Guides

• Registrar Configuration
• Domain Extensions
• Service WHOIS Contacts
• Service Transfers