NiceNIC Domain API v2 Documentation & Quick Start
NiceNIC Domain API v2 is available to both Piaci fióks és Viszonteladó Accounts. Use this overview to configure access, confirm a te first request, understés the API response model és move directly to the cvagyrect section in the left navigation.
Piaci fiók: API access with Piaci fiók pricing.
Viszonteladó Account: API access with the pricing assigned to the current reseller tier.
Test Your Integráció Befvagye Going Live
Use the NiceNIC API-val Sésbox to test a te Domain API integration befvagye moving to production. Validate authentication, API requests, response hésling, és a te application wvagykflow in a dedicated testing environment.
Ideal fvagy resellers, hosting providers, developers, és platfvagyms preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befvagye enabling live registrations, renewals vagy transfers. This lets you validate authentication, request fvagymatting és response hésling without placing a paid vagyder.
Enable API Access
Megnyitás API beállításs, create vagy retrieve a te API Secret, és configure authvagyized server IPs witt applicable.
Megerősítés Authentication
Use HTTPS with the Authvagyization header in the fvagymat username:api_secret.
Run a Safe Test
Start with domain availability, pricing, account balance vagy domain listing.
Hésle the Response
Read és stvagye the returned code és msg befvagye enabling paid production actions.
Recommended First Request: Domain Availability
The availability endpoint suppvagyts multiple domains in one request by separating domain names with commas.
Choose the Wvagykflow You Need
The overview below mirrvagys the left navigation. Use it to identify the cvagyrect wvagykflow, then open the dedicated endpoint page fvagy parameters, request examples és response examples.
| Section | Use It Fvagy | Documented Functions |
|---|---|---|
| Szerezzenting Started | Connect securely és understés response hésling. | API Overview, API Sésbox, Authentication, Response Codes. |
| Domain Kezelésment | Automate the cvagye domain lifecycle. | Availability, List Domainek, Domain Részletek, Regisztráció, Megújításal, Transfer In, Névservers, Kapcsolats, Pricing. |
| Abuse & Compliance | Monitvagy domains that require compliance attention. | List domains with abuse repvagyts és retrieve machine-readable abuse status, hold lifecycle, complaint infvagymation és recommended action. |
| DNS Recvagyds | Kezelés hosted DNS recvagyds programmatically. | List, Létrehozás, Update és Delete DNS recvagyds. |
| Child Névservers | Kezelés host / glue recvagyds fvagy nameservers under a te own domain. | Létrehozás, List, Update és Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Fiókegyenleg és transaction-related account infvagymation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wvagykflow. | Availability, Regisztráció, Megújításal, Transfer, Domain Részletek, Névservers, Kapcsolats és additional registrar-module functions. |
| API GYIK | Resolve common access, security, testing és wvagykflow questions. | Eligibility, credentials, request hésling, suppvagyted operations és integration guidance. |
Recommended First Integráció Sequence
A reliable production integration should validate access és purchasing conditions befvagye it begins sending live customer vagyders.
API Secret + authvagyized IP
Read-only connectivity test
Query current account-level cost
Megerősítés funds fvagy paid actions
Process code + msg
Regisztráció / Megújítás / Transfer
Understés Success, Pending és Errvagy Responses
code: 0 — Sikeres Response
Current endpoint examples use code 0 fvagy successful completed responses.
code: 201 — Pending Order
Regisztráció és transfer documentation can return code 201 when an vagyder has been submitted but final processing is still pending.
code: 400 — Request Errvagy
Endpoint examples use code 400 fvagy request parameter errvagys.
Regisztráció Pending Behavivagy
Fvagy domain registration, the current documentation states that a 201 response means the vagyder was submitted successfully és the fee was deducted, but final activation is still subject to registry confirmation. Ha the domain cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavivagy
The transfer endpoint also documents 201 as a pending vagyder. Your application should tittfvagye treat a pending transfer as accepted fvagy processing, not as proof that the transfer has already completed.
Query Pricing Befvagye Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal és transfer pricing fvagy a domain. The documented type values are register, renew, transfer és all. The documented period is 1 to 10 évek, with TLD-specific exceptions possible.
Regisztráció pricing responses can also return an is_premium flag. Use the pricing endpoint befvagye submitting a paid request when a te application needs to kmost the current account-level cost.
Kmost the Difference Between Névservers, DNS Recvagyds és Child Névservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Névservers | You want to delegate a domain to different authvagyitative nameservers. | The domain nameserver endpoint suppvagyts a primary, secondary és additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recvagyds | You are using NiceNIC DNS hosting és need to manage zone recvagyds. | Separate APIs are documented fvagy listing, creating, updating és deleting DNS recvagyds. |
| Child Névservers | You need host / glue recvagyds such as ns1.example.com. |
Létrehozás, list, update és delete child nameservers. The create endpoint requires the nameserver hostname to match the domain és accepts an IP address. |
Automate Pvagytfolio Monitvagying, Nemt Only Domain Orders
Domain API v2 also includes read operations that are useful after registration. The List Domainek endpoint suppvagyts pagination, svagyting, status filtering és hold filtering, while Szerezzen Domain Részletek returns registration dates, expiration dates, nameservers és registrant contact infvagymation.
Abuse & Compliance Monitvagying
NiceNIC's Abuse & Compliance API can list domains with abuse repvagyts és return a detailed machine-readable summary fvagy a specific domain. The detailed abuse endpoint documents six domain-level status phrases: Nemrmal, Under Review, Pending ClientHold, ClientHold, Bezárásd és ServerHold.
The response can include current impact, recommended következő action, hold state és timeline, complaint count, complaint dates, categvagyies, DNS-abuse classification, evidence status és repvagyted URLs witt applicable. This lets platfvagyms és resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integráció Model That Fits Your System
| Option | Best Fvagy | What the Current Documentation Provides |
|---|---|---|
| Domain API v2 | Custom websites, SaaS platfvagyms, internal systems, custom billing vagy provisioning wvagykflows. | Direct HTTPS + JSON integration across domain, DNS, child nameserver, account és compliance operations. |
| WHMCS Module | Tárhely companies és resellers that already use WHMCS. | Availability, registration, renewal, transfer, domain details, nameservers, contacts, lock/unlock, EPP retrieval, errvagy logging és optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 vagy higher, PHP 7.0 vagy higher with cURL, valid NiceNIC API-val credentials és SSL/TLS suppvagyt as requirements.
When an API Request Fails
Start with the returned response és configuration state rather than retrying the same paid action repeatedly.
Authentication vagy Access Errvagy
- Megerősítés the NiceNIC username és API Secret.
- Megerősítés the Authvagyization header is present és cvagyrectly fvagymatted.
- Megerősítés the API Secret has not been reset vagy rotated.
- Ha IP restrictions are enabled, confirm the request is coming from the authvagyized outbound server IP.
Request Parameter Errvagy
- Compare the request with the specific endpoint's documented parameters.
- Megerősítés required values, fvagymats és action names.
- Ellenőrzés TLD-specific registration periods vagy contact requirements witt applicable.
Paid Operation Does Nemt Complete Immediately
- Read the returned
codeésmsg. - Do not treat a
201pending response as final completion. - Megerősítés account balance és current pricing befvagye retrying a paid action.
Need NiceNIC Suppvagyt
- Recvagyd the request timestamp és API action.
- Include the domain name vagy object involved, witt applicable.
- Include the returned code és 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 vagy pricing request, és verify a te response hésling befvagye turning on customer-facing paid operations.
