NiceNIC Domēns API v2 Documentation & Quick Start

Test Your Integrācija Befvaie Going Live

Use the NiceNIC API Sunbox to test jūsu Domēns API integration befvaie moving to production. Validate authentication, API requests, response hunling, un jūsu application wvaikflow in a dedicated testing environment.

Ideal fvai resellers, hosting providers, developers, un platfvaims preparing an API integration.

Make Your First API Call in 4 Steps

Start with a read-only request befvaie enabling live registrations, renewals vai transfers. This lets you validate authentication, request fvaimatting un response hunling without placing a paid vaider.

Recommended First Request: Domēns Availability

The availability endpoint suppvaits multiple domēnss in one request by separating domēns names with commas.

Choose the Wvaikflow You Need

The overview below mirrvais the left navigation. Use it to identify the cvairect wvaikflow, then open the dedicated endpoint page fvai parameters, request examples un response examples.

Recommended First Integrācija Sequence

A reliable production integration should validate access un purchasing conditions befvaie it begins sending live customer vaiders.

Understun Veiksmīgi, Gaida apstiprinājumu un Errvai Responses

Reģistrācija Gaida apstiprinājumu Behavivai

Fvai domēns registration, the current documentation states that a 201 response means the vaider was submitted successfully un the fee was deducted, but final activation is still subject to registry confirmation. Ja the domēns cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Pārnest Gaida apstiprinājumu Behavivai

The transfer endpoint also documents 201 as a pending vaider. Your application should tšeitfvaie treat a pending transfer as accepted fvai processing, not as proof that the transfer has already completed.

Query Pricing Befvaie Paid Operations

NiceNIC's pricing endpoint can retrieve registration, renewal un transfer pricing fvai a domēns. The documented type values are register, renew, transfer un all. The documented period is 1 to 10 gadi, with TLD-specific exceptions possible.

Reģistrācija pricing responses can also return an is_premium flag. Use the pricing endpoint befvaie submitting a paid request when jūsu application needs to ktagad the current account-level cost.

Ktagad the Difference Between Nosaukumsservers, DNS ieraksti un Bērnu vārdu serveri

Automate Pvaitfolio Monitvaiing, Nēt Only Domēns Orders

Domēns API v2 also includes read operations that are useful after registration. The Saraksts Domēni endpoint suppvaits pagination, svaiting, status filtering un hold filtering, while Saņemt Domēns Detaļas returns registration dates, expiration dates, nameservers un registrant contact infvaimation.

Vardarbība un Atbilstība Monitvaiing

NiceNIC's Vardarbība un Atbilstība API can list domēnss with abuse repvaits un return a detailed machine-readable summary fvai a specific domēns. The detailed abuse endpoint documents six domēns-level status phrases: Nērmal, Under Review, Gaida apstiprinājumu ClientHold, ClientHold, Aizvērtd un ServerisHold.

The response can include current impact, recommended Nākamais darbība, hold state un timeline, complaint count, complaint dates, categvaiies, DNS-abuse classification, evidence status un repvaited URLs wšeit applicable. This lets platfvaims un resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Choose the Integrācija Model That Fits Your System

The current WHMCS documentation lists WHMCS 7.0 vai jaunāka versija, PHP 7.0 vai higher with cURL, valid NiceNIC API credentials un SSL/TLS suppvait as requirements.

When an API Request Fails

Start with the returned response un configuration state rather than retrying the same paid darbība repeatedly.