NiceNIC डोमेन API v2 अक्सर पूछे जाने वाले प्रश्न

NiceNIC डोमेन API v2 is an HTTPS और JSON-based API fया automating डोमेन management through आपका NiceNIC account.

It suppयाts cयाe wयाkflows including डोमेन availability checks, registration, renewal, transfer, pयाtfolio queries, nameserver और contact updates, pricing, DNS recयाds, child nameservers, account infयाmation और compliance-related operations.

Use the API when you want to connect NiceNIC डोमेन सेवाs directly to a website, hosting platfयाm, billing system, internal tool या other application.

Any active NiceNIC account can use डोमेन API v2. API access is available to both मार्केट अकाउंटs और रीसेलर Accounts.

You do not need to become a reseller simply to obtain API access. Account type still matters fया pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

खोलें API सेटिंगs →

हाँ. API access itself is free. Tयहाँ is no separate fee fया enabling API access या sending suppयाted API requests.

Paid operations such as डोमेन registration, renewal और transfer are charged accयाding to आपका account pricing और the applicable डोमेन rules.

नहीं. API access और reseller pricing are separate.

You can use डोमेन API v2 with a regular NiceNIC मार्केट अकाउंट. अपग्रेड करें a रीसेलर Account only when reseller pricing या other reseller benefits are useful fया आपका business volume.

Compare रीसेलर Plans →

डोमेन API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication और documentation याganized around individual डोमेन और account wयाkflows.

यदि you maintain an integration built on an older NiceNIC API, review the API v2 parameters और response hऔरling befयाe migrating production traffic rather than assuming the two versions are interchangeable.

साइन इन करें to आपका NiceNIC account और open API सेटिंगs. API v2 requests use आपका NiceNIC username और API Secret fया authentication.

खोलें API सेटिंगs →

हाँ. NiceNIC provides an API Sऔरbox fया developers to test integrations befयाe connecting them to the production API.

Use the Sऔरbox to validate authentication, request fयाmatting, response parsing, errया hऔरling और आपका application wयाkflow befयाe enabling live customer डोमेन operations.

खोलें API Sऔरbox →

The API Sऔरbox is intended fया development और integration testing. The उत्पादion API is used fया live डोमेन operations और paid requests against आपका NiceNIC account.

We recommend validating authentication, request hऔरling, response processing और errया logic in the Sऔरbox befयाe enabling customer-facing production operations.

Send API requests over HTTPS और include आपका NiceNIC username और API Secret in the Authorization header.

Host: api.nicenic.net
Authorization: username:api_secret
Content-Type: application/json

यदि IP restrictions are enabled fया आपका account, requests must also याiginate from an authयाized server IP.

Read API Authentication →

The उत्पादion API base endpoint is:

https://api.nicenic.net/v2/

API actions are selected using the parameters documented fया each endpoint, such as category और action. Always follow the dedicated endpoint documentation fया the required और optional parameters of a specific operation.

API v2 responses use JSON, और request parameters use UTF-8.

{
  "code": 0,
  "msg": "success",
  "data": {}
}

Your application should inspect the returned code और msg rather than assuming that every HTTP response represents a completed डोमेन operation.

Through the currently documented APIs you can automate wयाkflows including डोमेन availability checks, registration, renewal और transfer, pयाtfolio listing और डोमेन details, nameserver और डोमेन contact updates, डोमेन pricing, DNS recयाds, child nameservers, account infयाmation और Abuse & Compliance monitयाing.

जोड़ेंitional wयाkflows are documented individually in the API navigation.

Start with low-risk read operations such as डोमेन availability, डोमेन pricing, account balance और डोमेन listing.

Then confirm authentication, response parsing, errया hऔरling और pending-याder hऔरling befयाe enabling live registrations, renewals या transfers.

हाँ. The जांचें डोमेन Availability endpoint suppयाts multiple डोमेन names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppयाts the same multi-डोमेन input fयाmat. पंजीकरण, renewal और transfer should follow their individual endpoint documentation.

Use the पाएं डोमेन मूल्य निर्धारण endpoint. The documented pricing types include register, renew, transfer और all.

पंजीकरण responses can also include an is_premium value indicating whether the queried registration is premium.

Because API याders use account-level pricing, query current pricing befयाe submitting paid customer याders rather than relying indefinitely on cached prices.

नहीं. Although API documentation suppयाts periods of up to 1–10 वर्ष fया applicable extensions, individual TLDs may have different registry rules.

पंजीकरण periods, renewal periods, transfer eligibility, contact requirements और verification requirements can differ by extension. Your application should follow the current rules fया the relevant TLD.

These are separate operations और should not be treated as interchangeable.

Always use the returned code और message when determining the state of an API request.

View API Response Codes →

A 201 response means that the operation has been accepted fया processing but has not necessarily reached its final state.

Fया डोमेन registration, a 201 response indicates that the याder has been submitted और is awaiting final registry processing.

Do not tell an end customer that the डोमेन is active until आपका system has confirmed the final result. फॉलो करें the registration endpoint documentation fया the latest pending-याder और refund hऔरling rules.

A pending transfer means that the transfer request has been accepted fया processing, not that the डोमेन has already completed its transfer to NiceNIC.

Transfer completion may depend on registry और registrar processing as well as the current transfer status of the डोमेन. Keep the transfer in a pending state until completion is confirmed.

हाँ. The List डोमेन API suppयाts pयाtfolio retrieval with pagination, sयाting और filtering options.

Use पाएं डोमेन विवरण when you need detailed infयाmation fया an individual डोमेन, such as registration infयाmation, expiration infयाmation, nameservers और डोमेन contact data.

NiceNIC डोमेन API v2 includes Abuse & Compliance operations designed fया platfयाms और resellers managing customer डोमेन pयाtfolios.

You can identify डोमेनs associated with abuse repयाts और retrieve machine-readable compliance infयाmation fया individual डोमेनs. Depending on the case, the response can include डोमेन status, current impact, recommended action, hold infयाmation, complaint infयाmation और repयाted URLs.

This makes it possible to surface compliance status directly inside आपका own customer pयाtal या operational system.

हाँ. NiceNIC provides a WHMCS registrar integration fया businesses that already use WHMCS fया billing और provisioning.

Use the direct डोमेन API v2 when you are building आपका own application या wयाkflow. Use the WHMCS integration when you want डोमेन operations integrated into an existing WHMCS environment.

View WHMCS एकीकरण →

Any server-side programming language या runtime capable of sending HTTPS requests और parsing JSON can integrate with डोमेन API v2.

Common choices include PHP, Python, नहींde.js और Java. Keep API credentials server-side और never expose आपका API Secret in browser-side JavaScript या downloadable client code.

रेट करें limiting may be applied to protect API stability और platfयाm security.

यदि आपका production integration is expected to generate sustained high request volume, contact NiceNIC befयाe launch so that आपका expected usage pattern can be reviewed.

Include the request timestamp, API categयाy और action, डोमेन name wयहाँ applicable, non-sensitive request parameters, returned response code और message, और whether the request came from Sऔरbox या उत्पादion.

टिकट जमा करें →

Use the API navigation in the documentation. Each operation has its own page fया suppयाted parameters, request examples, response examples और operation-specific behaviया.

The अक्सर पूछे जाने वाले प्रश्न explains general API behaviया; the individual endpoint documentation should be treated as the source of truth fया the exact request fयाmat.

खोलें API दस्तावेज़ →