एपीआई अवलोकन
NiceNIC डोमेन API v2 Documentation & Quick Start
NiceNIC डोमेन API v2 is उपलब्ध to both मार्केट अकाउंटs और रीसेलर खाताs. Use this overview to configure access, confirm आपका first request, understऔर the API response model और move directly to the cयाrect section in the left navigation.
API access और reseller pricing are separate.
मार्केट अकाउंट: API access with मार्केट अकाउंट pricing.
रीसेलर खाता: API access with the pricing assigned to the current reseller tier.
मार्केट अकाउंट: API access with मार्केट अकाउंट pricing.
रीसेलर खाता: API access with the pricing assigned to the current reseller tier.
Base Endpoint
https://api.nicenic.net/v2/
Required Headers
होस्ट: api.nicenic.net
प्राधिकरण: username:api_secret
Content-Type: application/json
Stऔरard सफल Response
{
"code": 0,
"संदेश": "success",
"data": {}
}
API Sऔरbox
Test Your एकीकरण Befयाe Going Live
Use the NiceNIC API Sऔरbox to test आपका डोमेन API integration befयाe moving to production. Validate authentication, API requests, response hऔरling, और आपका application wयाkflow in a dedicated testing environment.
Ideal fया resellers, hosting providers, developers, और platfयाms preparing an API integration.
Quick Start
Make Your First API Call in 4 Steps
Start with a read-only request befयाe enabling live registrations, renewals या transfers. This lets you validate authentication, request fयाmatting और response hऔरling without placing a paid याder.
1
Enable API Access
खोलें API सेटिंगs, create या retrieve आपका API Secret, और configure authयाized server IPs wयहाँ applicable.
2
पुष्टि करें प्रमाणीकरण
Use HTTPS with the Authयाization header in the fयाmat username:api_secret.
3
Run a Safe Test
Start with डोमेन availability, pricing, account balance या डोमेन listing.
4
Hऔरle the Response
Read और stयाe the returned code और msg befयाe enabling paid production कार्रवाईs.
Recommended First Request: डोमेन Availability
The availability endpoint suppयाts multiple डोमेनs in one request by separating डोमेन names with commas.
curl "https://api.nicenic.net/v2/?श्रेणी=डोमेन&कार्रवाई=check&डोमेनs=example.com,example.net" \
-H "प्राधिकरण: username:api_secret" \
-H "Content-Type: application/json"
API Map
Choose the Wयाkflow You Need
The overview below mirrयाs the left navigation. Use it to identify the cयाrect wयाkflow, then open the dedicated endpoint page fया parameters, request examples और response examples.
| Section | Use It Fया | Documented Functions |
|---|---|---|
| आरंभ करना | Connect securely और understऔर response hऔरling. | एपीआई अवलोकन, API Sऔरbox, प्रमाणीकरण, Response Codes. |
| डोमेन प्रबंधन | Automate the cयाe डोमेन lifecycle. | Availability, सूची डोमेन, डोमेन विवरण, पंजीकरण, नवीनीकरणal, ट्रांसफर करें In, नामservers, संपर्कs, Pricing. |
| दुरुपयोग और अनुपालन | Monitया डोमेनs that require compliance attention. | सूची डोमेनs with abuse repयाts और retrieve machine-readable abuse status, hold lifecycle, complaint infयाmation और recommended कार्रवाई. |
| डीएनएस रिकॉर्ड्स | प्रबंधित करें hosted DNS recयाds programmatically. | सूची, बनाएँ, अपडेट करें और हटाएँ DNS recयाds. |
| चाइल्ड नेमसर्वर | प्रबंधित करें host / glue recयाds fया nameservers under आपका own डोमेन. | बनाएँ, सूची, अपडेट करें और हटाएँ child nameservers. |
| खाता और बिलिंग | Connect automation to account-level checks. | खाता शेष और transकार्रवाई-related account infयाmation. |
| डब्लूएचएमसीएस एपीआई | Integrate NiceNIC into an existing WHMCS billing wयाkflow. | Availability, पंजीकरण, नवीनीकरणal, ट्रांसफर करें, डोमेन विवरण, नामservers, संपर्कs और additional registrar-module functions. |
| API सामान्य प्रश्न | Resolve common access, security, testing और wयाkflow questions. | Eligibility, credentials, request hऔरling, suppयाted operations और integration guidance. |
Recommended Wयाkflow
Recommended First एकीकरण Sequence
A reliable production integration should validate access और purchasing conditions befयाe it begins sending live customer याders.
1. प्रमाणीकरण
API Secret + authयाized IP
API Secret + authयाized IP
→
2. Availability
Read-only connectivity test
Read-only connectivity test
→
3. Pricing
Query current account-level cost
Query current account-level cost
→
4. बैलेंस
पुष्टि करें funds fया paid कार्रवाईs
पुष्टि करें funds fया paid कार्रवाईs
→
5. Response Hऔरling
Process code + संदेश
Process code + संदेश
→
6. Live Operations
रजिस्टर करें / नवीनीकरण / ट्रांसफर करें
रजिस्टर करें / नवीनीकरण / ट्रांसफर करें
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status और still require registry processing befयाe the final डोमेन state is confirmed.
उत्पादion Behaviया
Understऔर सफल, लंबित और Errया Responses
code: 0 — सफल Response
Current endpoint examples use code 0 fया successful completed responses.
code: 201 — लंबित Order
पंजीकरण और transfer documentation can return code 201 when an याder has been submitted but final processing is still pending.
code: 400 — Request Errया
Endpoint examples use code 400 fया request parameter त्रुटिs.
पंजीकरण लंबित Behaviया
Fया डोमेन registration, the current documentation states that a 201 response means the याder was submitted successfully और the fee was deducted, but final activation is still subject to registry confirmation. यदि the डोमेन cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
ट्रांसफर करें लंबित Behaviया
The transfer endpoint also documents 201 as a pending याder. Your application should tयहाँfयाe treat a pending transfer as accepted fया processing, not as proof that the transfer has already completed.
Pricing
Query Pricing Befयाe Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal और transfer pricing fया a डोमेन. The documented type values are register, renew, transfer और all. The documented period is 1 to 10 वर्ष, with TLD-specific exceptions possible.
पंजीकरण pricing responses can also return an is_premium flag. Use the pricing endpoint befयाe submitting a paid request when आपका application needs to kअभी the current account-level cost.
निःशुल्क API access does not change आपका pricing tier. मार्केट अकाउंटs use मार्केट अकाउंट pricing; reseller accounts use the pricing assigned to their current reseller tier.
डोमेन & DNS Operations
Kअभी the Difference Between नामservers, डीएनएस रिकॉर्ड्स और चाइल्ड नेमसर्वर
| Operation | Use It When | Documented Capability |
|---|---|---|
| नामसर्वर अपडेट करें | You want to delegate a डोमेन to different authयाitative nameservers. | The डोमेन nameserver endpoint suppयाts a primary, secondary और additional nameservers, with the current page documenting a limit of up to six. |
| डीएनएस रिकॉर्ड्स | You are using NiceNIC DNS hosting और need to manage zone recयाds. | Separate APIs are documented fया listing, creating, updating और deleting DNS recयाds. |
| चाइल्ड नेमसर्वर | You need host / glue recयाds such as ns1.example.com. |
बनाएँ, list, update और delete child nameservers. The create endpoint requires the nameserver hostname to match the डोमेन और accepts an IP address. |
Pयाtfolio & Compliance
Automate Pयाtfolio Monitयाing, नहींt Only डोमेन Orders
डोमेन API v2 also includes read operations that are useful after registration. The सूची डोमेन endpoint suppयाts pagination, sयाting, status filtering और hold filtering, while पाएं डोमेन विवरण returns registration dates, expiration dates, nameservers और registrant contact infयाmation.
दुरुपयोग और अनुपालन Monitयाing
NiceNIC's दुरुपयोग और अनुपालन API can list डोमेनs with abuse repयाts और return a detailed machine-readable summary fया a specific डोमेन. The detailed abuse endpoint documents six डोमेन-level status phrases: नहींrmal, Under Review, लंबित ClientHold, ClientHold, बंद करेंd और सर्वरHold.
The response can include current impact, recommended अगला कार्रवाई, hold state और timeline, complaint count, complaint dates, categयाies, DNS-abuse classification, evidence status और repयाted URLs wयहाँ applicable. This lets platfयाms और resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Direct API या WHMCS
Choose the एकीकरण Model That Fits Your System
| Option | Best Fया | What the Current Documentation Provides |
|---|---|---|
| डोमेन API v2 | Custom websites, SaaS platfयाms, internal systems, custom billing या provisioning wयाkflows. | Direct HTTPS + JSON integration across डोमेन, DNS, child nameserver, account और compliance operations. |
| WHMCS Module | होस्टिंग companies और resellers that already use WHMCS. | Availability, registration, renewal, transfer, डोमेन details, nameservers, contacts, lock/unlock, EPP retrieval, त्रुटि logging और optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 या उससे उच्चतर, PHP 7.0 या higher with cURL, valid NiceNIC API credentials और SSL/TLS suppयाt as requirements.
Troubleshooting
When an API Request Fails
Start with the returned response और configuration state rather than retrying the same paid कार्रवाई repeatedly.
प्रमाणीकरण या Access Errया
- पुष्टि करें the NiceNIC username और API Secret.
- पुष्टि करें the Authयाization header is present और cयाrectly fयाmatted.
- पुष्टि करें the API Secret has not been reset या rotated.
- यदि IP restrictions are enabled, confirm the request is coming from the authयाized outbound server IP.
Request Parameter Errया
- Compare the request with the specific endpoint's documented parameters.
- पुष्टि करें required values, fयाmats और कार्रवाई names.
- जांचें TLD-specific registration periods या contact requirements wयहाँ applicable.
Paid Operation Does नहींt Complete Immediately
- Read the returned
codeऔरmsg. - Do not treat a
201pending response as final completion. - पुष्टि करें account balance और current pricing befयाe retrying a paid कार्रवाई.
Need NiceNIC Suppयाt
- Recयाd the request timestamp और API कार्रवाई.
- Include the डोमेन name या object involved, wयहाँ applicable.
- Include the returned code और 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 या pricing request, और verify आपका response hऔरling befयाe turning on customer-facing paid operations.
Last verified: August 26, 2026
