NiceNIC Domeen API v2 Korduma kippuvad küsimused

NiceNIC Domeen API v2 is an HTTPS ja JSON-based API fvõi automating domeen management through sinu NiceNIC account.

It suppvõits cvõie wvõikflows including domeen availability checks, registration, renewal, transfer, pvõitfolio queries, nameserver ja contact updates, pricing, DNS recvõids, child nameservers, account infvõimation ja compliance-related operations.

Use the API when you want to connect NiceNIC domeen teenuss directly to a website, hosting platfvõim, billing system, internal tool või other application.

Any active NiceNIC account can use Domeen API v2. API access is saadaval to both Turu kontos ja Järelmüüja Kontos.

You do not need to become a reseller simply to obtain API access. Konto type still matters fvõi pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

Ava API seadistuss →

Jah. API access itself is free. Tsiin is no separate fee fvõi enabling API access või sending suppvõited API requests.

Paid operations such as domeen registration, renewal ja transfer are charged accvõiding to sinu account pricing ja the applicable domeen rules.

Ei. API access ja reseller pricing are separate.

You can use Domeen API v2 with a regular NiceNIC Turu konto. Uuenda versioonile a Järelmüüja Konto only when reseller pricing või other reseller benefits are useful fvõi sinu business volume.

Compare Järelmüüja Plans →

Domeen API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication ja documentation võiganized around individual domeen ja account wvõikflows.

Kui you maintain an integration built on an older NiceNIC API, review the API v2 parameters ja response hjaling befvõie migrating production traffic rather than assuming the two versions are interchangeable.

Logi sisse to sinu NiceNIC account ja open API seadistuss. API v2 requests use sinu NiceNIC username ja API Secret fvõi authentication.

Ava API seadistuss →

Jah. NiceNIC provides an API Sjabox fvõi developers to test integrations befvõie connecting them to the production API.

Use the Sjabox to validate authentication, request fvõimatting, response parsing, viga hjaling ja sinu application wvõikflow befvõie enabling live customer domeen operations.

Ava API Sjabox →

The API Sjabox is intended fvõi development ja integration testing. The Toodeion API is used fvõi live domeen operations ja paid requests against sinu NiceNIC account.

We recommend validating authentication, request hjaling, response processing ja viga logic in the Sjabox befvõie enabling customer-facing production operations.

Send API requests over HTTPS ja include sinu NiceNIC username ja API Secret in the Authorization header.

Host: api.nicenic.net
Authorization: username:api_secret
Content-Type: application/json

Kui IP restrictions are enabled fvõi sinu account, requests must also võiiginate from an authvõiized server IP.

Read API Autentimine →

The Toodeion API base endpoint is:

https://api.nicenic.net/v2/

API tegevuss are selected using the parameters documented fvõi each endpoint, such as category ja action. Always follow the dedicated endpoint documentation fvõi the required ja optional parameters of a specific operation.

API v2 responses use JSON, ja request parameters use UTF-8.

{
  "code": 0,
  "msg": "success",
  "data": {}
}

Your application should inspect the returned code ja msg rather than assuming that every HTTP response represents a completed domeen operation.

Through the currently documented APIs you can automate wvõikflows including domeen availability checks, registration, renewal ja transfer, pvõitfolio listing ja domeen details, nameserver ja domeen contact updates, domeen pricing, DNS recvõids, child nameservers, account infvõimation ja Kuritarvitamine ja vastavus monitvõiing.

Lisaitional wvõikflows are documented individually in the API navigation.

Start with low-risk read operations such as domeen availability, domeen pricing, account balance ja domeen listing.

Then confirm authentication, response parsing, viga hjaling ja pending-võider hjaling befvõie enabling live registrations, renewals või transfers.

Jah. The Kontrolli domeeni saadavust endpoint suppvõits multiple domeen names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppvõits the same multi-domeen input fvõimat. Registreerimine, renewal ja transfer should follow their individual endpoint documentation.

Use the Hangi domeenihinnad endpoint. The documented pricing types include register, renew, transfer ja all.

Registreerimine responses can also include an is_premium value indicating whether the queried registration is premium.

Because API võiders use account-level pricing, query current pricing befvõie submitting paid customer võiders rather than relying indefinitely on cached prices.

Ei. Although API documentation suppvõits periods of up to 1–10 aastat fvõi applicable extensions, individual TLDs may have different registry rules.

Registreerimine periods, renewal periods, transfer eligibility, contact requirements ja verification requirements can differ by extension. Your application should follow the current rules fvõi the relevant TLD.

These are separate operations ja should not be treated as interchangeable.

Always use the returned code ja message when determining the state of an API request.

View API vastuse koodid →

A 201 response means that the operation has been accepted fvõi processing but has not necessarily reached its final state.

Fvõi domeen registration, a 201 response indicates that the võider has been submitted ja is awaiting final registry processing.

Do not tell an end customer that the domeen is active until sinu system has confirmed the final result. Jälgi the registration endpoint documentation fvõi the latest pending-võider ja refund hjaling rules.

A pending transfer means that the transfer request has been accepted fvõi processing, not that the domeen has already completed its transfer to NiceNIC.

Ühenda üle completion may depend on registry ja registrar processing as well as the current transfer status of the domeen. Keep the transfer in a pending state until completion is confirmed.

Jah. The Nimekiri Domeenid API suppvõits pvõitfolio retrieval with pagination, svõiting ja filtering options.

Use Hangi Domeen Detailid when you need detailed infvõimation fvõi an individual domeen, such as registration infvõimation, expiration infvõimation, nameservers ja domeen contact data.

NiceNIC Domeen API v2 includes Kuritarvitamine ja vastavus operations designed fvõi platfvõims ja resellers managing customer domeen pvõitfolios.

You can identify domeens associated with abuse repvõits ja retrieve machine-readable compliance infvõimation fvõi individual domeens. Depending on the case, the response can include domeen status, current impact, recommended tegevus, hold infvõimation, complaint infvõimation ja repvõited URLs.

This makes it possible to surface compliance status directly inside sinu own customer pvõital või operational system.

Jah. NiceNIC provides a WHMCS registrar integration fvõi businesses that already use WHMCS fvõi billing ja provisioning.

Use the direct Domeen API v2 when you are building sinu own application või wvõikflow. Use the WHMCS integration when you want domeen operations integrated into an existing WHMCS environment.

View WHMCS integratsioon →

Any server-side programming language või runtime capable of sending HTTPS requests ja parsing JSON can integrate with Domeen API v2.

Common choices include PHP, Python, Eide.js ja Java. Keep API credentials server-side ja never expose sinu API Secret in browser-side JavaScript või downloadable client code.

Hinnang limiting may be applied to protect API stability ja platfvõim security.

Kui sinu production integration is expected to generate sustained high request volume, contact NiceNIC befvõie launch so that sinu expected usage pattern can be reviewed.

Include the request timestamp, API kategooria ja tegevus, domeen name wsiin applicable, non-sensitive request parameters, returned response code ja message, ja whether the request came from Sjabox või Toodeion.

Esita päring →

Use the API navigation in the documentation. Each operation has its own page fvõi suppvõited parameters, request examples, response examples ja operation-specific behavivõi.

The KKK explains general API behavivõi; the individual endpoint documentation should be treated as the source of truth fvõi the exact request fvõimat.

Ava API dokumentatsioon →