NiceNIC Verkkotunnus API v2 Documentation & Quick Start

Test Your Integraatio Beftaie Going Live

Use the NiceNIC API Sjabox to test sinun Verkkotunnus API integration beftaie moving to production. Validate authentication, API requests, response hjaling, ja sinun application wtaikflow in a dedicated testing environment.

Ideal ftai resellers, hosting providers, developers, ja platftaims preparing an API integration.

Make Your First API Call in 4 Steps

Start with a read-only request beftaie enabling live registrations, renewals tai transfers. This lets you validate authentication, request ftaimatting ja response hjaling without placing a paid taider.

Recommended First Request: Verkkotunnus Availability

The availability endpoint supptaits multiple verkkotunnuss in one request by separating verkkotunnus names with commas.

Choose the Wtaikflow You Need

The overview below mirrtais the left navigation. Use it to identify the ctairect wtaikflow, then open the dedicated endpoint page ftai parameters, request examples ja response examples.

Recommended First Integraatio Sequence

A reliable production integration should validate access ja purchasing conditions beftaie it begins sending live customer taiders.

Understja Onnistui, Odottaa ja Errtai Responses

Rekisteröinti Odottaa Behavitai

Ftai verkkotunnus registration, the current documentation states that a 201 response means the taider was submitted successfully ja the fee was deducted, but final activation is still subject to registry confirmation. Jos the verkkotunnus cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Siirto Odottaa Behavitai

The transfer endpoint also documents 201 as a pending taider. Your application should ttässäftaie treat a pending transfer as accepted ftai processing, not as proof that the transfer has already completed.

Query Pricing Beftaie Paid Operations

NiceNIC's pricing endpoint can retrieve registration, renewal ja transfer pricing ftai a verkkotunnus. The documented type values are register, renew, transfer ja all. The documented period is 1 to 10 vuotta, with TLD-specific exceptions possible.

Rekisteröinti pricing responses can also return an is_premium flag. Use the pricing endpoint beftaie submitting a paid request when sinun application needs to knyt the current account-level cost.

Knyt the Difference Between Nimiservers, DNS-tietueet ja Lapsinimipalvelimet

Automate Ptaitfolio Monittaiing, Eit Only Verkkotunnus Orders

Verkkotunnus API v2 also includes read operations that are useful after registration. The Lista Verkkotunnukset endpoint supptaits pagination, staiting, status filtering ja hold filtering, while Hanki Verkkotunnus Tiedot returns registration dates, expiration dates, nameservers ja registrant contact inftaimation.

Väärinkäyttö & Noudattaminen Monittaiing

NiceNIC's Väärinkäyttö & Noudattaminen API can list verkkotunnuss with abuse reptaits ja return a detailed machine-readable summary ftai a specific verkkotunnus. The detailed abuse endpoint documents six verkkotunnus-level status phrases: Eirmal, Under Review, Odottaa ClientHold, ClientHold, Suljed ja PalvelinHold.

The response can include current impact, recommended seuraava toiminto, hold state ja timeline, complaint count, complaint dates, categtaiies, DNS-abuse classification, evidence status ja reptaited URLs wtässä applicable. This lets platftaims ja resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Choose the Integraatio Model That Fits Your System

The current WHMCS documentation lists WHMCS 7.0 tai uudempi, PHP 7.0 tai higher with cURL, valid NiceNIC API credentials ja SSL/TLS supptait as requirements.

When an API Request Fails

Start with the returned response ja configuration state rather than retrying the same paid toiminto repeatedly.