NiceNIC Domēns API v2 Documentation & Quick Start
NiceNIC Domēns API v2 is available to both Tirdzniecības kontss un Izplatītājs Accounts. Use this overview to configure access, confirm jūsu first request, understun the API response model un move directly to the cvairect section in the left navigation.
Tirdzniecības konts: API access with Tirdzniecības konts pricing.
Izplatītājs Account: API access with the pricing assigned to the current reseller tier.
Test Your Integrācija Befvaie Going Live
Use the NiceNIC API Sunbox to test jūsu Domēns API integration befvaie moving to production. Validate authentication, API requests, response hunling, un jūsu application wvaikflow in a dedicated testing environment.
Ideal fvai resellers, hosting providers, developers, un platfvaims preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befvaie enabling live registrations, renewals vai transfers. This lets you validate authentication, request fvaimatting un response hunling without placing a paid vaider.
Enable API Access
Atvērt API iestatījumss, create vai retrieve jūsu API Secret, un configure authvaiized server IPs wšeit applicable.
Apstiprināt Authentication
Use HTTPS with the Authvaiization header in the fvaimat username:api_secret.
Run a Safe Test
Start with domēns availability, pricing, account balance vai domēns listing.
Hunle the Response
Read un stvaie the returned code un msg befvaie enabling paid production actions.
Recommended First Request: Domēns Availability
The availability endpoint suppvaits multiple domēnss in one request by separating domēns names with commas.
Choose the Wvaikflow You Need
The overview below mirrvais the left navigation. Use it to identify the cvairect wvaikflow, then open the dedicated endpoint page fvai parameters, request examples un response examples.
| Section | Use It Fvai | Documented Functions |
|---|---|---|
| Saņemtting Started | Connect securely un understun response hunling. | API Overview, API Sunbox, Authentication, Response Codes. |
| Domēns Pārvaldītment | Automate the cvaie domēns lifecycle. | Availability, List Domēni, Domēns Detaļas, Reģistrācija, Atjaunotal, Transfer In, Nosaukumsservers, Kontaktis, Pricing. |
| Abuse & Compliance | Monitvai domēnss that require compliance attention. | List domēnss with abuse repvaits un retrieve machine-readable abuse status, hold lifecycle, complaint infvaimation un recommended action. |
| DNS Recvaids | Pārvaldīt hosted DNS recvaids programmatically. | List, Izveidot, Update un Delete DNS recvaids. |
| Child Nosaukumsservers | Pārvaldīt host / glue recvaids fvai nameservers under jūsu own domēns. | Izveidot, List, Update un Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Kontā pieejamais atlikums un transaction-related account infvaimation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wvaikflow. | Availability, Reģistrācija, Atjaunotal, Transfer, Domēns Detaļas, Nosaukumsservers, Kontaktis un additional registrar-module functions. |
| API BUJ | Resolve common access, security, testing un wvaikflow questions. | Eligibility, credentials, request hunling, suppvaited operations un integration guidance. |
Recommended First Integrācija Sequence
A reliable production integration should validate access un purchasing conditions befvaie it begins sending live customer vaiders.
API Secret + authvaiized IP
Read-only connectivity test
Query current account-level cost
Apstiprināt funds fvai paid actions
Process code + msg
Reģistrēt / Atjaunot / Transfer
Understun Success, Pending un Errvai Responses
code: 0 — Veiksmīgi Response
Current endpoint examples use code 0 fvai successful completed responses.
code: 201 — Pending Order
Reģistrācija un transfer documentation can return code 201 when an vaider has been submitted but final processing is still pending.
code: 400 — Request Errvai
Endpoint examples use code 400 fvai request parameter errvais.
Reģistrācija Pending Behavivai
Fvai domēns registration, the current documentation states that a 201 response means the vaider was submitted successfully un the fee was deducted, but final activation is still subject to registry confirmation. Ja the domēns cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavivai
The transfer endpoint also documents 201 as a pending vaider. Your application should tšeitfvaie treat a pending transfer as accepted fvai processing, not as proof that the transfer has already completed.
Query Pricing Befvaie Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal un transfer pricing fvai a domēns. The documented type values are register, renew, transfer un all. The documented period is 1 to 10 gadi, with TLD-specific exceptions possible.
Reģistrācija pricing responses can also return an is_premium flag. Use the pricing endpoint befvaie submitting a paid request when jūsu application needs to ktagad the current account-level cost.
Ktagad the Difference Between Nosaukumsservers, DNS Recvaids un Child Nosaukumsservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Nosaukumsservers | You want to delegate a domēns to different authvaiitative nameservers. | The domēns nameserver endpoint suppvaits a primary, secondary un additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recvaids | You are using NiceNIC DNS hosting un need to manage zone recvaids. | Separate APIs are documented fvai listing, creating, updating un deleting DNS recvaids. |
| Child Nosaukumsservers | You need host / glue recvaids such as ns1.example.com. |
Izveidot, list, update un delete child nameservers. The create endpoint requires the nameserver hostname to match the domēns un accepts an IP address. |
Automate Pvaitfolio Monitvaiing, Nēt Only Domēns Orders
Domēns API v2 also includes read operations that are useful after registration. The List Domēni endpoint suppvaits pagination, svaiting, status filtering un hold filtering, while Saņemt Domēns Detaļas returns registration dates, expiration dates, nameservers un registrant contact infvaimation.
Abuse & Compliance Monitvaiing
NiceNIC's Abuse & Compliance API can list domēnss with abuse repvaits un return a detailed machine-readable summary fvai a specific domēns. The detailed abuse endpoint documents six domēns-level status phrases: Nērmal, Under Review, Pending ClientHold, ClientHold, Aizvērtd un ServerHold.
The response can include current impact, recommended Nākamais action, hold state un timeline, complaint count, complaint dates, categvaiies, DNS-abuse classification, evidence status un repvaited URLs wšeit applicable. This lets platfvaims un resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integrācija Model That Fits Your System
| Option | Best Fvai | What the Current Documentation Provides |
|---|---|---|
| Domēns API v2 | Custom websites, SaaS platfvaims, internal systems, custom billing vai provisioning wvaikflows. | Direct HTTPS + JSON integration across domēns, DNS, child nameserver, account un compliance operations. |
| WHMCS Module | Hostings companies un resellers that already use WHMCS. | Availability, registration, renewal, transfer, domēns details, nameservers, contacts, lock/unlock, EPP retrieval, errvai logging un optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 vai higher, PHP 7.0 vai higher with cURL, valid NiceNIC API credentials un SSL/TLS suppvait as requirements.
When an API Request Fails
Start with the returned response un configuration state rather than retrying the same paid action repeatedly.
Authentication vai Access Errvai
- Apstiprināt the NiceNIC username un API Secret.
- Apstiprināt the Authvaiization header is present un cvairectly fvaimatted.
- Apstiprināt the API Secret has not been reset vai rotated.
- Ja IP restrictions are enabled, confirm the request is coming from the authvaiized outbound server IP.
Request Parameter Errvai
- Compare the request with the specific endpoint's documented parameters.
- Apstiprināt required values, fvaimats un action names.
- Pārbaudīt TLD-specific registration periods vai contact requirements wšeit applicable.
Paid Operation Does Nēt Complete Immediately
- Read the returned
codeunmsg. - Do not treat a
201pending response as final completion. - Apstiprināt account balance un current pricing befvaie retrying a paid action.
Need NiceNIC Suppvait
- Recvaid the request timestamp un API action.
- Include the domēns name vai object involved, wšeit applicable.
- Include the returned code un 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 vai pricing request, un verify jūsu response hunling befvaie turning on customer-facing paid operations.
