NiceNIC Домен API v2 Documentation & Quick Start
NiceNIC Домен API v2 is available to both Ринковий акаунтs і Реселер Accounts. Use this overview to configure access, confirm ваш first request, understі the API response model і move directly to the cабоrect section in the left navigation.
Ринковий акаунт: API access with Ринковий акаунт pricing.
Реселер Account: API access with the pricing assigned to the current reseller tier.
Test Your Інтеграція Befабоe Going Live
Use the NiceNIC API Sіbox to test ваш Домен API integration befабоe moving to production. Validate authentication, API requests, response hіling, і ваш application wабоkflow in a dedicated testing environment.
Ideal fабо resellers, hosting providers, developers, і platfабоms preparing an API integration.
Make Your First API 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 API Access
Відкрити Налаштування APIs, create або retrieve ваш API 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. | API Overview, API 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 API | Integrate NiceNIC into an existing WHMCS billing wабоkflow. | Availability, Реєстрація, Продовжитиal, Transfer, Домен Деталі, Ім’яservers, Контактs і additional registrar-module functions. |
| API Поширені питання | 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.
API 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 APIs 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
Домен API 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 API 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 |
|---|---|---|
| Домен API 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 API Request Fails
Start with the returned response і configuration state rather than retrying the same paid action repeatedly.
Authentication або Access Errабо
- Підтвердити the NiceNIC username і API Secret.
- Підтвердити the Authабоization header is present і cабоrectly fабоmatted.
- Підтвердити the API 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 і API action.
- Include the домен name або object involved, wтут applicable.
- Include the returned code і message.
- Share non-sensitive parameters only; never post the full API Secret in a ticket.
Start with a Safe Test Request
Enable API access, confirm authentication, run an availability або pricing request, і verify ваш response hіling befабоe turning on customer-facing paid operations.
