NiceNIC Domenas API v2 Documentation & Quick Start
NiceNIC Domenas API v2 is available to both Rinkos paskyras ir Platintojas Accounts. Use this overview to configure access, confirm jūsų first request, understir the API response model ir move directly to the carrect section in the left navigation.
Rinkos paskyra: API access with Rinkos paskyra pricing.
Platintojas Account: API access with the pricing assigned to the current reseller tier.
Test Your Integracija Befare Going Live
Use the NiceNIC API Sirbox to test jūsų Domenas API integration befare moving to production. Validate authentication, API requests, response hirling, ir jūsų application warkflow in a dedicated testing environment.
Ideal far resellers, hosting providers, developers, ir platfarms preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befare enabling live registrations, renewals ar transfers. This lets you validate authentication, request farmatting ir response hirling without placing a paid arder.
Enable API Access
Atidaryti API nustatymais, create ar retrieve jūsų API Secret, ir configure autharized server IPs wčia applicable.
Patvirtinti Authentication
Use HTTPS with the Autharization header in the farmat username:api_secret.
Run a Safe Test
Start with domenas availability, pricing, account balance ar domenas listing.
Hirle the Response
Read ir stare the returned code ir msg befare enabling paid production actions.
Recommended First Request: Domenas Availability
The availability endpoint supparts multiple domenass in one request by separating domenas names with commas.
Choose the Warkflow You Need
The overview below mirrars the left navigation. Use it to identify the carrect warkflow, then open the dedicated endpoint page far parameters, request examples ir response examples.
| Section | Use It Far | Documented Functions |
|---|---|---|
| Gaukiteting Started | Connect securely ir understir response hirling. | API Overview, API Sirbox, Authentication, Response Codes. |
| Domenas Tvarkytiment | Automate the care domenas lifecycle. | Availability, List Domenai, Domenas Detalės, Registracija, Atnaujintial, Transfer In, Vardasservers, Kontaktais, Pricing. |
| Abuse & Compliance | Monitar domenass that require compliance attention. | List domenass with abuse reparts ir retrieve machine-readable abuse status, hold lifecycle, complaint infarmation ir recommended action. |
| DNS Recards | Tvarkyti hosted DNS recards programmatically. | List, Sukurti, Update ir Delete DNS recards. |
| Child Vardasservers | Tvarkyti host / glue recards far nameservers under jūsų own domenas. | Sukurti, List, Update ir Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Sąskaitos likutis ir transaction-related account infarmation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing warkflow. | Availability, Registracija, Atnaujintial, Transfer, Domenas Detalės, Vardasservers, Kontaktais ir additional registrar-module functions. |
| API DUK | Resolve common access, security, testing ir warkflow questions. | Eligibility, credentials, request hirling, supparted operations ir integration guidance. |
Recommended First Integracija Sequence
A reliable production integration should validate access ir purchasing conditions befare it begins sending live customer arders.
API Secret + autharized IP
Read-only connectivity test
Query current account-level cost
Patvirtinti funds far paid actions
Process code + msg
Registruotis / Atnaujinti / Transfer
Understir Success, Pending ir Errar Responses
code: 0 — Sėkminga Response
Current endpoint examples use code 0 far successful completed responses.
code: 201 — Pending Order
Registracija ir transfer documentation can return code 201 when an arder has been submitted but final processing is still pending.
code: 400 — Request Errar
Endpoint examples use code 400 far request parameter errars.
Registracija Pending Behaviar
Far domenas registration, the current documentation states that a 201 response means the arder was submitted successfully ir the fee was deducted, but final activation is still subject to registry confirmation. Jei the domenas cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behaviar
The transfer endpoint also documents 201 as a pending arder. Your application should tčiafare treat a pending transfer as accepted far processing, not as proof that the transfer has already completed.
Query Pricing Befare Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal ir transfer pricing far a domenas. The documented type values are register, renew, transfer ir all. The documented period is 1 to 10 metų, with TLD-specific exceptions possible.
Registracija pricing responses can also return an is_premium flag. Use the pricing endpoint befare submitting a paid request when jūsų application needs to kdabar the current account-level cost.
Kdabar the Difference Between Vardasservers, DNS Recards ir Child Vardasservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Vardasservers | You want to delegate a domenas to different autharitative nameservers. | The domenas nameserver endpoint supparts a primary, secondary ir additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recards | You are using NiceNIC DNS hosting ir need to manage zone recards. | Separate APIs are documented far listing, creating, updating ir deleting DNS recards. |
| Child Vardasservers | You need host / glue recards such as ns1.example.com. |
Sukurti, list, update ir delete child nameservers. The create endpoint requires the nameserver hostname to match the domenas ir accepts an IP address. |
Automate Partfolio Monitaring, Net Only Domenas Orders
Domenas API v2 also includes read operations that are useful after registration. The List Domenai endpoint supparts pagination, sarting, status filtering ir hold filtering, while Gaukite Domenas Detalės returns registration dates, expiration dates, nameservers ir registrant contact infarmation.
Abuse & Compliance Monitaring
NiceNIC's Abuse & Compliance API can list domenass with abuse reparts ir return a detailed machine-readable summary far a specific domenas. The detailed abuse endpoint documents six domenas-level status phrases: Nermal, Under Review, Pending ClientHold, ClientHold, Uždarytid ir ServerHold.
The response can include current impact, recommended toliau action, hold state ir timeline, complaint count, complaint dates, categaries, DNS-abuse classification, evidence status ir reparted URLs wčia applicable. This lets platfarms ir resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integracija Model That Fits Your System
| Option | Best Far | What the Current Documentation Provides |
|---|---|---|
| Domenas API v2 | Custom websites, SaaS platfarms, internal systems, custom billing ar provisioning warkflows. | Direct HTTPS + JSON integration across domenas, DNS, child nameserver, account ir compliance operations. |
| WHMCS Module | Talpinimas companies ir resellers that already use WHMCS. | Availability, registration, renewal, transfer, domenas details, nameservers, contacts, lock/unlock, EPP retrieval, errar logging ir optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 ar higher, PHP 7.0 ar higher with cURL, valid NiceNIC API credentials ir SSL/TLS suppart as requirements.
When an API Request Fails
Start with the returned response ir configuration state rather than retrying the same paid action repeatedly.
Authentication ar Access Errar
- Patvirtinti the NiceNIC username ir API Secret.
- Patvirtinti the Autharization header is present ir carrectly farmatted.
- Patvirtinti the API Secret has not been reset ar rotated.
- Jei IP restrictions are enabled, confirm the request is coming from the autharized outbound server IP.
Request Parameter Errar
- Compare the request with the specific endpoint's documented parameters.
- Patvirtinti required values, farmats ir action names.
- Patikrinti TLD-specific registration periods ar contact requirements wčia applicable.
Paid Operation Does Net Complete Immediately
- Read the returned
codeirmsg. - Do not treat a
201pending response as final completion. - Patvirtinti account balance ir current pricing befare retrying a paid action.
Need NiceNIC Suppart
- Recard the request timestamp ir API action.
- Include the domenas name ar object involved, wčia applicable.
- Include the returned code ir 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 ar pricing request, ir verify jūsų response hirling befare turning on customer-facing paid operations.
