NiceNIC Domenas API v2 Dažniausiai užduodami klausimai

NiceNIC Domenas API v2 is an HTTPS ir JSON-based API far automating domenas management through jūsų NiceNIC account.

It supparts care warkflows including domenas availability checks, registration, renewal, transfer, partfolio queries, nameserver ir contact updates, pricing, DNS recards, child nameservers, account infarmation ir compliance-related operations.

Use the API when you want to connect NiceNIC domenas paslaugas directly to a website, hosting platfarm, billing system, internal tool ar other application.

Any active NiceNIC account can use Domenas API v2. API access is available to both Rinkos paskyras ir Platintojas Accounts.

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

Atidaryti API nustatymais →

Taip. API access itself is free. Tčia is no separate fee far enabling API access ar sending supparted API requests.

Paid operations such as domenas registration, renewal ir transfer are charged accarding to jūsų account pricing ir the applicable domenas rules.

Ne. API access ir reseller pricing are separate.

You can use Domenas API v2 with a regular NiceNIC Rinkos paskyra. Atnaujinti į a Platintojas Account only when reseller pricing ar other reseller benefits are useful far jūsų business volume.

Compare Platintojas Plans →

Domenas API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication ir documentation arganized around individual domenas ir account warkflows.

Jei you maintain an integration built on an older NiceNIC API, review the API v2 parameters ir response hirling befare migrating production traffic rather than assuming the two versions are interchangeable.

Prisijungti to jūsų NiceNIC account ir open API nustatymais. API v2 requests use jūsų NiceNIC username ir API Secret far authentication.

Atidaryti API nustatymais →

Taip. NiceNIC provides an API Sirbox far developers to test integrations befare connecting them to the production API.

Use the Sirbox to validate authentication, request farmatting, response parsing, errar hirling ir jūsų application warkflow befare enabling live customer domenas operations.

Atidaryti API Sirbox →

The API Sirbox is intended far development ir integration testing. The Produktasion API is used far live domenas operations ir paid requests against jūsų NiceNIC account.

We recommend validating authentication, request hirling, response processing ir errar logic in the Sirbox befare enabling customer-facing production operations.

Send API requests over HTTPS ir include jūsų NiceNIC username ir API Secret in the Authorization header.

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

Jei IP restrictions are enabled far jūsų account, requests must also ariginate from an autharized server IP.

Read API Authentication →

The Produktasion API base endpoint is:

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

API actions are selected using the parameters documented far each endpoint, such as category ir action. Always follow the dedicated endpoint documentation far the required ir optional parameters of a specific operation.

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

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

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

Through the currently documented APIs you can automate warkflows including domenas availability checks, registration, renewal ir transfer, partfolio listing ir domenas details, nameserver ir domenas contact updates, domenas pricing, DNS recards, child nameservers, account infarmation ir Abuse & Compliance monitaring.

Pridėtiitional warkflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, errar hirling ir pending-arder hirling befare enabling live registrations, renewals ar transfers.

Taip. The Patikrinti Domenas Availability endpoint supparts multiple domenas names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation supparts the same multi-domenas input farmat. Registracija, renewal ir transfer should follow their individual endpoint documentation.

Use the Gaukite Domenų kainoraštis endpoint. The documented pricing types include register, renew, transfer ir all.

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

Because API arders use account-level pricing, query current pricing befare submitting paid customer arders rather than relying indefinitely on cached prices.

Ne. Although API documentation supparts periods of up to 1–10 metų far applicable extensions, individual TLDs may have different registry rules.

Registracija periods, renewal periods, transfer eligibility, contact requirements ir verification requirements can differ by extension. Your application should follow the current rules far the relevant TLD.

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

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

View API Response Codes →

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

Far domenas registration, a 201 response indicates that the arder has been submitted ir is awaiting final registry processing.

Do not tell an end customer that the domenas is active until jūsų system has confirmed the final result. Sekti the registration endpoint documentation far the latest pending-arder ir refund hirling rules.

A pending transfer means that the transfer request has been accepted far processing, not that the domenas has already completed its transfer to NiceNIC.

Transfer completion may depend on registry ir registrar processing as well as the current transfer status of the domenas. Keep the transfer in a pending state until completion is confirmed.

Taip. The List Domenai API supparts partfolio retrieval with pagination, sarting ir filtering options.

Use Gaukite Domenas Detalės when you need detailed infarmation far an individual domenas, such as registration infarmation, expiration infarmation, nameservers ir domenas contact data.

NiceNIC Domenas API v2 includes Abuse & Compliance operations designed far platfarms ir resellers managing customer domenas partfolios.

You can identify domenass associated with abuse reparts ir retrieve machine-readable compliance infarmation far individual domenass. Depending on the case, the response can include domenas status, current impact, recommended action, hold infarmation, complaint infarmation ir reparted URLs.

This makes it possible to surface compliance status directly inside jūsų own customer partal ar operational system.

Taip. NiceNIC provides a WHMCS registrar integration far businesses that already use WHMCS far billing ir provisioning.

Use the direct Domenas API v2 when you are building jūsų own application ar warkflow. Use the WHMCS integration when you want domenas operations integrated into an existing WHMCS environment.

View WHMCS integracija →

Any server-side programming language ar runtime capable of sending HTTPS requests ir parsing JSON can integrate with Domenas API v2.

Common choices include PHP, Python, Nede.js ir Java. Keep API credentials server-side ir never expose jūsų API Secret in browser-side JavaScript ar downloadable client code.

Įvertinimas limiting may be applied to protect API stability ir platfarm security.

Jei jūsų production integration is expected to generate sustained high request volume, contact NiceNIC befare launch so that jūsų expected usage pattern can be reviewed.

Include the request timestamp, API categary ir action, domenas name wčia applicable, non-sensitive request parameters, returned response code ir message, ir whether the request came from Sirbox ar Produktasion.

Pateikti užklausą →

Use the API navigation in the documentation. Each operation has its own page far supparted parameters, request examples, response examples ir operation-specific behaviar.

The DUK explains general API behaviar; the individual endpoint documentation should be treated as the source of truth far the exact request farmat.

Atidaryti API dokumentacija →