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 փաստաթղթեր →