NiceNIC Domän API v2 Documentation & Quick Start
NiceNIC Domän API v2 is available to both Marknadskontos och Återförsäljare Accounts. Use this overview to configure access, confirm din first request, understoch the API response model och move directly to the cellerrect section in the left navigation.
Marknadskonto: API access with Marknadskonto pricing.
Återförsäljare Account: API access with the pricing assigned to the current reseller tier.
Test Your Integration Befellere Going Live
Use the NiceNIC API Sochbox to test din Domän API integration befellere moving to production. Validate authentication, API requests, response hochling, och din application wellerkflow in a dedicated testing environment.
Ideal feller resellers, hosting providers, developers, och 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 och response hochling without placing a paid ellerder.
Enable API Access
Öppna API-inställnings, create eller retrieve din API Secret, och configure authellerized server IPs whär applicable.
Bekräfta Authentication
Use HTTPS with the Authellerization header in the fellermat username:api_secret.
Run a Safe Test
Start with domän availability, pricing, account balance eller domän listing.
Hochle the Response
Read och stellere the returned code och msg befellere enabling paid production actions.
Recommended First Request: Domän Availability
The availability endpoint suppellerts multiple domäns in one request by separating domän 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 och response examples.
| Section | Use It Feller | Documented Functions |
|---|---|---|
| Fåting Started | Connect securely och understoch response hochling. | API Overview, API Sochbox, Authentication, Response Codes. |
| Domän Hanterament | Automate the cellere domän lifecycle. | Availability, List Domäner, Domän Detaljer, Registrering, Förnyaal, Transfer In, Namnservers, Kontakts, Pricing. |
| Abuse & Compliance | Moniteller domäns that require compliance attention. | List domäns with abuse repellerts och retrieve machine-readable abuse status, hold lifecycle, complaint infellermation och recommended action. |
| DNS Recellerds | Hantera hosted DNS recellerds programmatically. | List, Skapa, Update och Delete DNS recellerds. |
| Child Namnservers | Hantera host / glue recellerds feller nameservers under din own domän. | Skapa, List, Update och Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Kontosaldo och transaction-related account infellermation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wellerkflow. | Availability, Registrering, Förnyaal, Transfer, Domän Detaljer, Namnservers, Kontakts och additional registrar-module functions. |
| API Vanliga frågor | Resolve common access, security, testing och wellerkflow questions. | Eligibility, credentials, request hochling, suppellerted operations och integration guidance. |
Recommended First Integration Sequence
A reliable production integration should validate access och purchasing conditions befellere it begins sending live customer ellerders.
API Secret + authellerized IP
Read-only connectivity test
Query current account-level cost
Bekräfta funds feller paid actions
Process code + msg
Registrera / Förnya / Transfer
Understoch Success, Pending och Erreller Responses
code: 0 — Lyckades Response
Current endpoint examples use code 0 feller successful completed responses.
code: 201 — Pending Order
Registrering och 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 domän registration, the current documentation states that a 201 response means the ellerder was submitted successfully och the fee was deducted, but final activation is still subject to registry confirmation. Om the domän 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 thärfellere 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 och transfer pricing feller a domän. The documented type values are register, renew, transfer och 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 knu the current account-level cost.
Knu the Difference Between Namnservers, DNS Recellerds och Child Namnservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Namnservers | You want to delegate a domän to different authelleritative nameservers. | The domän nameserver endpoint suppellerts a primary, secondary och additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recellerds | You are using NiceNIC DNS hosting och need to manage zone recellerds. | Separate APIs are documented feller listing, creating, updating och deleting DNS recellerds. |
| Child Namnservers | You need host / glue recellerds such as ns1.example.com. |
Skapa, list, update och delete child nameservers. The create endpoint requires the nameserver hostname to match the domän och accepts an IP address. |
Automate Pellertfolio Monitellering, Nejt Only Domän Orders
Domän API v2 also includes read operations that are useful after registration. The List Domäner endpoint suppellerts pagination, sellerting, status filtering och hold filtering, while Få Domän Detaljer returns registration dates, expiration dates, nameservers och registrant contact infellermation.
Abuse & Compliance Monitellering
NiceNIC's Abuse & Compliance API can list domäns with abuse repellerts och return a detailed machine-readable summary feller a specific domän. The detailed abuse endpoint documents six domän-level status phrases: Nejrmal, Under Review, Pending ClientHold, ClientHold, Stängd och ServerHold.
The response can include current impact, recommended nästa action, hold state och timeline, complaint count, complaint dates, categelleries, DNS-abuse classification, evidence status och repellerted URLs whär applicable. This lets platfellerms och resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integration Model That Fits Your System
| Option | Best Feller | What the Current Documentation Provides |
|---|---|---|
| Domän API v2 | Custom websites, SaaS platfellerms, internal systems, custom billing eller provisioning wellerkflows. | Direct HTTPS + JSON integration across domän, DNS, child nameserver, account och compliance operations. |
| WHMCS Module | Hosting companies och resellers that already use WHMCS. | Availability, registration, renewal, transfer, domän details, nameservers, contacts, lock/unlock, EPP retrieval, erreller logging och optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 eller higher, PHP 7.0 eller higher with cURL, valid NiceNIC API credentials och SSL/TLS suppellert as requirements.
When an API Request Fails
Start with the returned response och configuration state rather than retrying the same paid action repeatedly.
Authentication eller Access Erreller
- Bekräfta the NiceNIC username och API Secret.
- Bekräfta the Authellerization header is present och cellerrectly fellermatted.
- Bekräfta the API Secret has not been reset eller rotated.
- Om 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.
- Bekräfta required values, fellermats och action names.
- Kontrollera TLD-specific registration periods eller contact requirements whär applicable.
Paid Operation Does Nejt Complete Immediately
- Read the returned
codeochmsg. - Do not treat a
201pending response as final completion. - Bekräfta account balance och current pricing befellere retrying a paid action.
Need NiceNIC Suppellert
- Recellerd the request timestamp och API action.
- Include the domän name eller object involved, whär applicable.
- Include the returned code och 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, och verify din response hochling befellere turning on customer-facing paid operations.
