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.

Отворен Настройка на APIs →

Да. 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 Настройка на APIs. API v2 requests use вашия NiceNIC username и API Secret fили authentication.

Отворен Настройка на APIs →

Да. 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 документация →