NiceNIC Домен API v2 Поширені запитання

NiceNIC Домен API v2 is an HTTPS і JSON-based API fабо automating домен management through ваш NiceNIC account.

It suppабоts cабоe wабоkflows including домен availability checks, registration, renewal, transfer, pабоtfolio queries, nameserver і contact updates, pricing, DNS recабоds, child nameservers, account infабоmation і compliance-related operations.

Use the API when you want to connect NiceNIC домен послугаs directly to a website, hosting platfабоm, billing system, internal tool або other application.

Any active NiceNIC account can use Домен API v2. API access is доступний to both Ринковий акаунтs і Реселер Рахунокs.

You do not need to become a reseller simply to obtain API access. Рахунок type still matters fабо pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

Відкрити Налаштування APIs →

Так. API access itself is free. Tтут is no separate fee fабо enabling API access або sending suppабоted API requests.

Paid operations such as домен registration, renewal і transfer are charged accабоding to ваш account pricing і the applicable домен rules.

Ні. API access і reseller pricing are separate.

You can use Домен API v2 with a regular NiceNIC Ринковий акаунт. Перейти на вищий рівень a Реселер Рахунок only when reseller pricing або other reseller benefits are useful fабо ваш business volume.

Compare Реселер Plans →

Домен API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication і documentation абоganized around individual домен і account wабоkflows.

Якщо you maintain an integration built on an older NiceNIC API, review the API v2 parameters і response hіling befабоe migrating production traffic rather than assuming the two versions are interchangeable.

Вхід to ваш NiceNIC account і open Налаштування APIs. API v2 requests use ваш NiceNIC username і API Secret fабо authentication.

Відкрити Налаштування APIs →

Так. NiceNIC provides an API Sіbox fабо developers to test integrations befабоe connecting them to the production API.

Use the Sіbox to validate authentication, request fабоmatting, response parsing, помилка hіling і ваш application wабоkflow befабоe enabling live customer домен operations.

Відкрити API Sіbox →

The API Sіbox is intended fабо development і integration testing. The Товарion API is used fабо live домен operations і paid requests against ваш NiceNIC account.

We recommend validating authentication, request hіling, response processing і помилка logic in the Sіbox befабоe enabling customer-facing production operations.

Send API requests over HTTPS і include ваш NiceNIC username і API Secret in the Authorization header.

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

Якщо IP restrictions are enabled fабо ваш account, requests must also абоiginate from an authабоized server IP.

Read API Аутентифікація →

The Товарion API base endpoint is:

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

API діяs are selected using the parameters documented fабо each endpoint, such as category і action. Always follow the dedicated endpoint documentation fабо the required і optional parameters of a specific operation.

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

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

Your application should inspect the returned code і msg rather than assuming that every HTTP response represents a completed домен operation.

Through the currently documented APIs you can automate wабоkflows including домен availability checks, registration, renewal і transfer, pабоtfolio listing і домен details, nameserver і домен contact updates, домен pricing, DNS recабоds, child nameservers, account infабоmation і Зловживання та відповідність monitабоing.

Додатиitional wабоkflows are documented individually in the API navigation.

Start with low-risk read operations such as домен availability, домен pricing, account balance і домен listing.

Then confirm authentication, response parsing, помилка hіling і pending-абоder hіling befабоe enabling live registrations, renewals або transfers.

Так. The Перевірити доступність домену endpoint suppабоts multiple домен names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppабоts the same multi-домен input fабоmat. Реєстрація, renewal і transfer should follow their individual endpoint documentation.

Use the Отримати ціни на домени endpoint. The documented pricing types include register, renew, transfer і all.

Реєстрація responses can also include an is_premium value indicating whether the queried registration is premium.

Because API абоders use account-level pricing, query current pricing befабоe submitting paid customer абоders rather than relying indefinitely on cached prices.

Ні. Although API documentation suppабоts periods of up to 1–10 років fабо applicable extensions, individual TLDs may have different registry rules.

Реєстрація periods, renewal periods, transfer eligibility, contact requirements і verification requirements can differ by extension. Your application should follow the current rules fабо the relevant TLD.

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

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

View Коди відповідей API →

A 201 response means that the operation has been accepted fабо processing but has not necessarily reached its final state.

Fабо домен registration, a 201 response indicates that the абоder has been submitted і is awaiting final registry processing.

Do not tell an end customer that the домен is active until ваш system has confirmed the final result. Слідкувати the registration endpoint documentation fабо the latest pending-абоder і refund hіling rules.

A pending transfer means that the transfer request has been accepted fабо processing, not that the домен has already completed its transfer to NiceNIC.

Передати completion may depend on registry і registrar processing as well as the current transfer status of the домен. Keep the transfer in a pending state until completion is confirmed.

Так. The Список Домени API suppабоts pабоtfolio retrieval with pagination, sабоting і filtering options.

Use Отримати Домен Деталі when you need detailed infабоmation fабо an individual домен, such as registration infабоmation, expiration infабоmation, nameservers і домен contact data.

NiceNIC Домен API v2 includes Зловживання та відповідність operations designed fабо platfабоms і resellers managing customer домен pабоtfolios.

You can identify доменs associated with abuse repабоts і retrieve machine-readable compliance infабоmation fабо individual доменs. Depending on the case, the response can include домен status, current impact, recommended дія, hold infабоmation, complaint infабоmation і repабоted URLs.

This makes it possible to surface compliance status directly inside ваш own customer pабоtal або operational system.

Так. NiceNIC provides a WHMCS registrar integration fабо businesses that already use WHMCS fабо billing і provisioning.

Use the direct Домен API v2 when you are building ваш own application або wабоkflow. Use the WHMCS integration when you want домен operations integrated into an existing WHMCS environment.

View Інтеграція з WHMCS →

Any server-side programming language або runtime capable of sending HTTPS requests і parsing JSON can integrate with Домен API v2.

Common choices include PHP, Python, Ніde.js і Java. Keep API credentials server-side і never expose ваш API Secret in browser-side JavaScript або downloadable client code.

Рейтинг limiting may be applied to protect API stability і platfабоm security.

Якщо ваш production integration is expected to generate sustained high request volume, contact NiceNIC befабоe launch so that ваш expected usage pattern can be reviewed.

Include the request timestamp, API категорія і дія, домен name wтут applicable, non-sensitive request parameters, returned response code і message, і whether the request came from Sіbox або Товарion.

Відправити запит →

Use the API navigation in the documentation. Each operation has its own page fабо suppабоted parameters, request examples, response examples і operation-specific behaviабо.

The Питання та відповіді explains general API behaviабо; the individual endpoint documentation should be treated as the source of truth fабо the exact request fабоmat.

Відкрити Документація API →