NiceNIC Domæne API v2 Documentation & Quick Start

Test Your Integration Befellere Going Live

Use the NiceNIC API Sogbox to test din Domæne API integration befellere moving to production. Validate authentication, API requests, response hogling, og din application wellerkflow in a dedicated testing environment.

Ideal feller resellers, hosting providers, developers, og platfellerms preparing an API integration.

Make Your First API Call in 4 Steps

Start with a read-only request befellere enabling live registrations, renewals eller transfers. This lets you validate authentication, request fellermatting og response hogling without placing a paid ellerder.

Recommended First Request: Domæne Availability

The availability endpoint suppellerts multiple domænes in one request by separating domæne names with commas.

Choose the Wellerkflow You Need

The overview below mirrellers the left navigation. Use it to identify the cellerrect wellerkflow, then open the dedicated endpoint page feller parameters, request examples og response examples.

Recommended First Integration Sequence

A reliable production integration should validate access og purchasing conditions befellere it begins sending live customer ellerders.

Understog Succes, Afventer og Erreller Responses

Registrering Afventer Behavieller

Feller domæne registration, the current documentation states that a 201 response means the ellerder was submitted successfully og the fee was deducted, but final activation is still subject to registry confirmation. Hvis the domæne cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Overfør Afventer Behavieller

The transfer endpoint also documents 201 as a pending ellerder. Your application should therfellere treat a pending transfer as accepted feller processing, not as proof that the transfer has already completed.

Query Pricing Befellere Paid Operations

NiceNIC's pricing endpoint can retrieve registration, renewal og transfer pricing feller a domæne. The documented type values are register, renew, transfer og all. The documented period is 1 to 10 år, with TLD-specific exceptions possible.

Registrering pricing responses can also return an is_premium flag. Use the pricing endpoint befellere submitting a paid request when din application needs to knu the current account-level cost.

Knu the Difference Between Navnservers, DNS-poster og Børnenavneservere

Automate Pellertfolio Monitellering, Nejt Only Domæne Orders

Domæne API v2 also includes read operations that are useful after registration. The Liste Domæner endpoint suppellerts pagination, sellerting, status filtering og hold filtering, while Få Domæne Detaljer returns registration dates, expiration dates, nameservers og registrant contact infellermation.

Misbrug & Overholdelse Monitellering

NiceNIC's Misbrug & Overholdelse API can list domænes with abuse repellerts og return a detailed machine-readable summary feller a specific domæne. The detailed abuse endpoint documents six domæne-level status phrases: Nejrmal, Under Review, Afventer ClientHold, ClientHold, Lukd og ServerHold.

The response can include current impact, recommended næste handling, hold state og timeline, complaint count, complaint dates, categelleries, DNS-abuse classification, evidence status og repellerted URLs wher applicable. This lets platfellerms og resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Choose the Integration Model That Fits Your System

The current WHMCS documentation lists WHMCS 7.0 eller nyere, PHP 7.0 eller higher with cURL, valid NiceNIC API credentials og SSL/TLS suppellert as requirements.

When an API Request Fails

Start with the returned response og configuration state rather than retrying the same paid handling repeatedly.