NiceNIC Domene API v2 Documentation & Quick Start
NiceNIC Domene API v2 is available to both Markeds kontos og Forhandler Accounts. Use this overview to configure access, confirm din first request, understog the API response model og move directly to the cellerrect section in the left navigation.
Markeds konto: API access with Markeds konto pricing.
Forhandler Account: API access with the pricing assigned to the current reseller tier.
Test Your Integrering Befellere Going Live
Use the NiceNIC API Sogbox to test din Domene API integration befellere moving to production. Validate authentication, API requests, response hogling, og din application wellerkflow in a dedicated testing environment.
Ideal feller resellers, hosting providers, developers, og platfellerms preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befellere enabling live registrations, renewals eller transfers. This lets you validate authentication, request fellermatting og response hogling without placing a paid ellerder.
Enable API Access
Åpen API-innstillings, create eller retrieve din API Secret, og configure authellerized server IPs wher applicable.
Bekreft Authentication
Use HTTPS with the Authellerization header in the fellermat username:api_secret.
Run a Safe Test
Start with domenet availability, pricing, account balance eller domenet listing.
Hogle the Response
Read og stellere the returned code og msg befellere enabling paid production actions.
Recommended First Request: Domene Availability
The availability endpoint suppellerts multiple domenets in one request by separating domenet names with commas.
Choose the Wellerkflow You Need
The overview below mirrellers the left navigation. Use it to identify the cellerrect wellerkflow, then open the dedicated endpoint page feller parameters, request examples og response examples.
| Section | Use It Feller | Documented Functions |
|---|---|---|
| Fåting Started | Connect securely og understog response hogling. | API Overview, API Sogbox, Authentication, Response Codes. |
| Domene Administrerment | Automate the cellere domenet lifecycle. | Availability, List Domenenavn, Domene Detaljer, Registrering, Fornyal, Transfer In, Navnservers, Kontakts, Pricing. |
| Abuse & Compliance | Moniteller domenets that require compliance attention. | List domenets with abuse repellerts og retrieve machine-readable abuse status, hold lifecycle, complaint infellermation og recommended action. |
| DNS Recellerds | Administrer hosted DNS recellerds programmatically. | List, Opprett, Update og Delete DNS recellerds. |
| Child Navnservers | Administrer host / glue recellerds feller nameservers under din own domenet. | Opprett, List, Update og Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Kontosaldo og transaction-related account infellermation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wellerkflow. | Availability, Registrering, Fornyal, Transfer, Domene Detaljer, Navnservers, Kontakts og additional registrar-module functions. |
| API Ofte stilte spørsmål | Resolve common access, security, testing og wellerkflow questions. | Eligibility, credentials, request hogling, suppellerted operations og integration guidance. |
Recommended First Integrering Sequence
A reliable production integration should validate access og purchasing conditions befellere it begins sending live customer ellerders.
API Secret + authellerized IP
Read-only connectivity test
Query current account-level cost
Bekreft funds feller paid actions
Process code + msg
Registrer / Forny / Transfer
Understog Success, Pending og Erreller Responses
code: 0 — Vellykket Response
Current endpoint examples use code 0 feller successful completed responses.
code: 201 — Pending Order
Registrering og transfer documentation can return code 201 when an ellerder has been submitted but final processing is still pending.
code: 400 — Request Erreller
Endpoint examples use code 400 feller request parameter errellers.
Registrering Pending Behavieller
Feller domenet registration, the current documentation states that a 201 response means the ellerder was submitted successfully og the fee was deducted, but final activation is still subject to registry confirmation. Hvis the domenet cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavieller
The transfer endpoint also documents 201 as a pending ellerder. Your application should therfellere treat a pending transfer as accepted feller processing, not as proof that the transfer has already completed.
Query Pricing Befellere Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal og transfer pricing feller a domenet. The documented type values are register, renew, transfer og all. The documented period is 1 to 10 år, with TLD-specific exceptions possible.
Registrering pricing responses can also return an is_premium flag. Use the pricing endpoint befellere submitting a paid request when din application needs to knå the current account-level cost.
Knå the Difference Between Navnservers, DNS Recellerds og Child Navnservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Navnservers | You want to delegate a domenet to different authelleritative nameservers. | The domenet nameserver endpoint suppellerts a primary, secondary og additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recellerds | You are using NiceNIC DNS hosting og need to manage zone recellerds. | Separate APIs are documented feller listing, creating, updating og deleting DNS recellerds. |
| Child Navnservers | You need host / glue recellerds such as ns1.example.com. |
Opprett, list, update og delete child nameservers. The create endpoint requires the nameserver hostname to match the domenet og accepts an IP address. |
Automate Pellertfolio Monitellering, Neit Only Domene Orders
Domene API v2 also includes read operations that are useful after registration. The List Domenenavn endpoint suppellerts pagination, sellerting, status filtering og hold filtering, while Få Domene Detaljer returns registration dates, expiration dates, nameservers og registrant contact infellermation.
Abuse & Compliance Monitellering
NiceNIC's Abuse & Compliance API can list domenets with abuse repellerts og return a detailed machine-readable summary feller a specific domenet. The detailed abuse endpoint documents six domenet-level status phrases: Neirmal, Under Review, Pending ClientHold, ClientHold, Lukkd og ServerHold.
The response can include current impact, recommended neste action, hold state og timeline, complaint count, complaint dates, categelleries, DNS-abuse classification, evidence status og repellerted URLs wher applicable. This lets platfellerms og resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integrering Model That Fits Your System
| Option | Best Feller | What the Current Documentation Provides |
|---|---|---|
| Domene API v2 | Custom websites, SaaS platfellerms, internal systems, custom billing eller provisioning wellerkflows. | Direct HTTPS + JSON integration across domenet, DNS, child nameserver, account og compliance operations. |
| WHMCS Module | Hosting companies og resellers that already use WHMCS. | Availability, registration, renewal, transfer, domenet details, nameservers, contacts, lock/unlock, EPP retrieval, erreller logging og optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 eller higher, PHP 7.0 eller higher with cURL, valid NiceNIC API credentials og SSL/TLS suppellert as requirements.
When an API Request Fails
Start with the returned response og configuration state rather than retrying the same paid action repeatedly.
Authentication eller Access Erreller
- Bekreft the NiceNIC username og API Secret.
- Bekreft the Authellerization header is present og cellerrectly fellermatted.
- Bekreft the API Secret has not been reset eller rotated.
- Hvis IP restrictions are enabled, confirm the request is coming from the authellerized outbound server IP.
Request Parameter Erreller
- Compare the request with the specific endpoint's documented parameters.
- Bekreft required values, fellermats og action names.
- Sjekk TLD-specific registration periods eller contact requirements wher applicable.
Paid Operation Does Neit Complete Immediately
- Read the returned
codeogmsg. - Do not treat a
201pending response as final completion. - Bekreft account balance og current pricing befellere retrying a paid action.
Need NiceNIC Suppellert
- Recellerd the request timestamp og API action.
- Include the domenet name eller object involved, wher applicable.
- Include the returned code og 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 eller pricing request, og verify din response hogling befellere turning on customer-facing paid operations.
