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 қолжетімді to both Нарықтық шотs және Өкіл Есептік жазбаs.

You do not need to become a reseller simply to obtain API access. Есептік жазба 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 Өкіл Есептік жазба 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, қате пайда болды 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 және қате пайда болды 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 Растау →

The Өнімion API base endpoint is:

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

API әрекетs 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 және Зәбір & Саясатқа сай болу 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, қате пайда болды hжәнеling және pending-немесеder hжәнеling befнемесеe enabling live registrations, renewals немесе transfers.

Иә. The Доменнің қолжетімділігін тексеру 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 жауап кодтары →

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.

Аудару 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 Тізім Домендер 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 Зәбір & Саясатқа сай болу 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 әрекет, 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 санат және әрекет, домен 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 құжаттамасы →