NiceNIC Домен АПИ v2 Часто задаваемые вопросы

NiceNIC Домен АПИ v2 is an HTTPS А JSON-based АПИ 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 АПИ 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 Домен АПИ v2. АПИ access is домен доступен для регистрации to both Рыночный счетs А Реселлер Аккаунтs.

You do not need to become a reseller simply to obtain АПИ access. Аккаунт type still matters f Или pricing: paid АПИ operations use the pricing assigned to the NiceNIC account sending the request.

Нормально открыт API Настройкаs →

Да. АПИ access itself is free. Tздесь is no separate fee f Или enabling АПИ access Или sending supp Илиted АПИ requests.

Paid operations such as Доменное имя registration, renewal А transfer are charged acc Илиding to Твой account pricing А the applicable Доменное имя rules.

Нет!. АПИ access А reseller pricing are separate.

You can use Домен АПИ v2 with a regular NiceNIC Рыночный счет. Обновите до a Реселлер Аккаунт only when reseller pricing Или other reseller benefits are useful f Или Твой business volume.

Compare Реселлер Plans →

Домен АПИ 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 АПИ v2 parameters А response hАling bef Илиe migrating production traffic rather than assuming the two versions are interchangeable.

Войти to Твой NiceNIC account А open API Настройкаs. АПИ v2 requests use Твой NiceNIC username А АПИ Secret f Или authentication.

Нормально открыт API Настройкаs →

Да. NiceNIC provides an АПИ SАbox f Или developers to test integrations bef Илиe connecting them to the production АПИ.

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

Нормально открыт АПИ SАbox →

The АПИ SАbox is intended f Или development А integration testing. The Продуктовый центрion АПИ 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 АПИ requests over HTTPS А include Твой NiceNIC username А АПИ 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 АПИ Аутентификация →

The Продуктовый центрion АПИ base endpoint is:

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

АПИ действие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.

АПИ 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 АПИs 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 АПИ 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 АПИ 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 АПИ Илиders use account-level pricing, query current pricing bef Илиe submitting paid customer Илиders rather than relying indefinitely on cached prices.

Нет!. Although АПИ 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 АПИ 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 List Доменами АПИ 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 Домен АПИ 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 Домен АПИ 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 Домен АПИ v2.

Common choices include PHP, Python, Нет!de.js А Java. Keep АПИ credentials server-side А never expose Твой АПИ Secret in browser-side JavaScript Или downloadable client code.

Оценить limiting may be applied to protect АПИ 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, АПИ категория А действие, Доменное имя name wздесь applicable, non-sensitive request parameters, returned response code А message, А whether the request came from SАbox Или Продуктовый центрion.

Отправить запрос →

Use the АПИ navigation in the documentation. Each operation has its own page f Или supp Илиted parameters, request examples, response examples А operation-specific behavi Или.

The Часто задаваемые вопросы explains general АПИ behavi Или; the individual endpoint documentation should be treated as the source of truth f Или the exact request f Илиmat.

Нормально открыт Файл АПИ →