NiceNIC Домен АПИ v2 Documentation & Quick Start
NiceNIC Домен АПИ v2 is available to both Рыночный счетs А Реселлер Accounts. Use this overview to configure access, confirm Твой first request, understА the АПИ response model А move directly to the c Илиrect section in the left navigation.
Рыночный счет: АПИ access with Рыночный счет pricing.
Реселлер Account: АПИ access with the pricing assigned to the current reseller tier.
Test Your Интеграция Bef Илиe Going Live
Use the NiceNIC API SАbox to test Твой Домен АПИ integration bef Илиe moving to production. Validate authentication, АПИ requests, response hАling, А Твой application w Илиkflow in a dedicated testing environment.
Ideal f Или resellers, hosting providers, developers, А platf Илиms preparing an АПИ integration.
Make Your First АПИ Call in 4 Steps
Start with a read-only request bef Илиe enabling live registrations, renewals Или transfers. This lets you validate authentication, request f Илиmatting А response hАling without placing a paid Илиder.
Enable АПИ Access
Нормально открыт API Настройкаs, create Или retrieve Твой АПИ Secret, А configure auth Илиized server IPs wздесь applicable.
Подтвердить Authentication
Use HTTPS with the Auth Илиization header in the f Илиmat username:api_secret.
Run a Safe Test
Start with Доменное имя availability, pricing, account balance Или Доменное имя listing.
HАle the Response
Read А st Илиe the returned code А msg bef Илиe enabling paid production actions.
Recommended First Request: Домен Availability
The availability endpoint supp Илиts multiple Доменное имяs in one request by separating Доменное имя names with commas.
Choose the W Илиkflow You Need
The overview below mirr Илиs the left navigation. Use it to identify the c Илиrect w Илиkflow, then open the dedicated endpoint page f Или parameters, request examples А response examples.
| Section | Use It F Или | Documented Functions |
|---|---|---|
| Доступting Started | Connect securely А understА response hАling. | АПИ Overview, АПИ SАbox, Authentication, Response Codes. |
| Домен Управлениеment | Automate the c Илиe Доменное имя lifecycle. | Availability, List Доменами, Домен Детали, Регистрация, Продлениеal, Transfer In, Имяservers, Контактная информацияs, Pricing. |
| Abuse & Compliance | Monit Или Доменное имяs that require compliance attention. | List Доменное имяs with abuse rep Илиts А retrieve machine-readable abuse status, hold lifecycle, complaint inf Илиmation А recommended action. |
| DNS Rec Илиds | Управление hosted DNS rec Илиds programmatically. | List, Создание, Update А Delete DNS rec Илиds. |
| Child Имяservers | Управление host / glue rec Илиds f Или nameservers under Твой own Доменное имя. | Создание, List, Update А Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Сальдо счета А transaction-related account inf Илиmation. |
| WHMCS АПИ | Integrate NiceNIC into an existing WHMCS billing w Илиkflow. | Availability, Регистрация, Продлениеal, Transfer, Домен Детали, Имяservers, Контактная информацияs А additional registrar-module functions. |
| АПИ Вопросы и ответы | Resolve common access, security, testing А w Илиkflow questions. | Eligibility, credentials, request hАling, supp Илиted operations А integration guidance. |
Recommended First Интеграция Sequence
A reliable production integration should validate access А purchasing conditions bef Илиe it begins sending live customer Илиders.
АПИ Secret + auth Илиized IP
Read-only connectivity test
Query current account-level cost
Подтвердить funds f Или paid actions
Process code + msg
Регистрация / Продление / Transfer
UnderstА Success, Pending А Err Или Responses
code: 0 — Успех Response
Current endpoint examples use code 0 f Или successful completed responses.
code: 201 — Pending Order
Регистрация А transfer documentation can return code 201 when an Илиder has been submitted but final processing is still pending.
code: 400 — Request Err Или
Endpoint examples use code 400 f Или request parameter err Илиs.
Регистрация Pending Behavi Или
F Или Доменное имя registration, the current documentation states that a 201 response means the Илиder was submitted successfully А the fee was deducted, but final activation is still subject to registry confirmation. Если the Доменное имя cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavi Или
The transfer endpoint also documents 201 as a pending Илиder. Your application should tздесьf Илиe treat a pending transfer as accepted f Или processing, not as proof that the transfer has already completed.
Query Pricing Bef Илиe Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal А transfer pricing f Или a Доменное имя. The documented type values are register, renew, transfer А all. The documented period is 1 to 10 годы, with TLD-specific exceptions possible.
Регистрация pricing responses can also return an is_premium flag. Use the pricing endpoint bef Илиe submitting a paid request when Твой application needs to kсейчас the current account-level cost.
Kсейчас the Difference Between Имяservers, DNS Rec Илиds А Child Имяservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Имяservers | You want to delegate a Доменное имя to different auth Илиitative nameservers. | The Доменное имя nameserver endpoint supp Илиts a primary, secondary А additional nameservers, with the current page documenting a limit of up to six. |
| DNS Rec Илиds | You are using NiceNIC DNS hosting А need to manage zone rec Илиds. | Separate АПИs are documented f Или listing, creating, updating А deleting DNS rec Илиds. |
| Child Имяservers | You need host / glue rec Илиds such as ns1.example.com. |
Создание, list, update А delete child nameservers. The create endpoint requires the nameserver hostname to match the Доменное имя А accepts an IP address. |
Automate P Илиtfolio Monit Илиing, Нет!t Only Домен Orders
Домен АПИ v2 also includes read operations that are useful after registration. The List Доменами endpoint supp Илиts pagination, s Илиting, status filtering А hold filtering, while Доступ Домен Детали returns registration dates, expiration dates, nameservers А registrant contact inf Илиmation.
Abuse & Compliance Monit Илиing
NiceNIC's Abuse & Compliance АПИ can list Доменное имяs with abuse rep Илиts А return a detailed machine-readable summary f Или a specific Доменное имя. The detailed abuse endpoint documents six Доменное имя-level status phrases: Нет!rmal, Under Review, Pending ClientHold, ClientHold, Закрытьd А ServerHold.
The response can include current impact, recommended следующий action, hold state А timeline, complaint count, complaint dates, categ Илиies, DNS-abuse classification, evidence status А rep Илиted URLs wздесь applicable. This lets platf Илиms А resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Интеграция Model That Fits Your System
| Option | Best F Или | What the Current Documentation Provides |
|---|---|---|
| Домен АПИ v2 | Custom websites, SaaS platf Илиms, internal systems, custom billing Или provisioning w Илиkflows. | Direct HTTPS + JSON integration across Доменное имя, DNS, child nameserver, account А compliance operations. |
| WHMCS Module | Хостинг companies А resellers that already use WHMCS. | Availability, registration, renewal, transfer, Доменное имя details, nameservers, contacts, lock/unlock, EPP retrieval, err Или logging А optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 Или higher, PHP 7.0 Или higher with cURL, valid NiceNIC API credentials А SSL/TLS supp Илиt as requirements.
When an АПИ Request Fails
Start with the returned response А configuration state rather than retrying the same paid action repeatedly.
Authentication Или Access Err Или
- Подтвердить the NiceNIC username А АПИ Secret.
- Подтвердить the Auth Илиization header is present А c Илиrectly f Илиmatted.
- Подтвердить the АПИ Secret has not been reset Или rotated.
- Если IP restrictions are enabled, confirm the request is coming from the auth Илиized outbound server IP.
Request Parameter Err Или
- Compare the request with the specific endpoint's documented parameters.
- Подтвердить required values, f Илиmats А action names.
- Проверка TLD-specific registration periods Или contact requirements wздесь applicable.
Paid Operation Does Нет!t Complete Immediately
- Read the returned
codeАmsg. - Do not treat a
201pending response as final completion. - Подтвердить account balance А current pricing bef Илиe retrying a paid action.
Need NiceNIC Supp Илиt
- Rec Илиd the request timestamp А АПИ action.
- Include the Доменное имя name Или object involved, wздесь applicable.
- Include the returned code А message.
- Share non-sensitive parameters only; never post the full АПИ Secret in a ticket.
Start with a Safe Test Request
Enable АПИ access, confirm authentication, run an availability Или pricing request, А verify Твой response hАling bef Илиe turning on customer-facing paid operations.
