NiceNIC Domen API v2 Tez-tez so‘raladigan savollar

NiceNIC Domen API v2 is an HTTPS va JSON-based API fyoki automating domain management through sizning NiceNIC account.

It suppyokits cyokie wyokikflows including domain availability checks, registration, renewal, transfer, pyokitfolio queries, nameserver va contact updates, pricing, DNS recyokids, child nameservers, account infyokimation va compliance-related operations.

Use the API when you want to connect NiceNIC domain Xizmats directly to a website, hosting platfyokim, billing system, internal tool yoki other application.

Any active NiceNIC account can use Domen API v2. API access is mavjud to both Market Hisobis va Reseller Hisobs.

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

Ochish API Sozlamasis →

Ha. API access itself is free. Tbu yerni is no separate fee fyoki enabling API access yoki sending suppyokited API requests.

Paid operations such as domain registration, renewal va transfer are charged accyokiding to sizning account pricing va the applicable domain rules.

Yo‘q. API access va reseller pricing are separate.

You can use Domen API v2 with a regular NiceNIC Market Hisobi. Yangilash a Reseller Hisob only when reseller pricing yoki other reseller benefits are useful fyoki sizning business volume.

Compare Reseller Plans →

Domen API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication va documentation yokiganized around individual domain va account wyokikflows.

Agar you maintain an integration built on an older NiceNIC API, review the API v2 parameters va response hvaling befyokie migrating production traffic rather than assuming the two versions are interchangeable.

Kirish to sizning NiceNIC account va open API Sozlamasis. API v2 requests use sizning NiceNIC username va API Secret fyoki authentication.

Ochish API Sozlamasis →

Ha. NiceNIC provides an API Svabox fyoki developers to test integrations befyokie connecting them to the production API.

Use the Svabox to validate authentication, request fyokimatting, response parsing, xato hvaling va sizning application wyokikflow befyokie enabling live customer domain operations.

Ochish API Svabox →

The API Svabox is intended fyoki development va integration testing. The Маҳсулотion API is used fyoki live domain operations va paid requests against sizning NiceNIC account.

We recommend validating authentication, request hvaling, response processing va xato logic in the Svabox befyokie enabling customer-facing production operations.

Send API requests over HTTPS va include sizning NiceNIC username va API Secret in the Authorization header.

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

Agar IP restrictions are enabled fyoki sizning account, requests must also yokiiginate from an authyokiized server IP.

Read API Tasdiqlash →

The Маҳсулотion API base endpoint is:

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

API harakats are selected using the parameters documented fyoki each endpoint, such as category va action. Always follow the dedicated endpoint documentation fyoki the required va optional parameters of a specific operation.

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

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

Your application should inspect the returned code va msg rather than assuming that every HTTP response represents a completed domain operation.

Through the currently documented APIs you can automate wyokikflows including domain availability checks, registration, renewal va transfer, pyokitfolio listing va domain details, nameserver va domain contact updates, domain pricing, DNS recyokids, child nameservers, account infyokimation va Zulm va Amalga Oshirish monityokiing.

Qo‘shishitional wyokikflows are documented individually in the API navigation.

Start with low-risk read operations such as domain availability, domain pricing, account balance va domain listing.

Then confirm authentication, response parsing, xato hvaling va pending-yokider hvaling befyokie enabling live registrations, renewals yoki transfers.

Ha. The Domen mavjudligini tekshirish endpoint suppyokits multiple domain names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppyokits the same multi-domain input fyokimat. Ro‘yxatdan o‘tish, renewal va transfer should follow their individual endpoint documentation.

Use the Domen narxlarini olish endpoint. The documented pricing types include register, renew, transfer va all.

Ro‘yxatdan o‘tish responses can also include an is_premium value indicating whether the queried registration is premium.

Because API yokiders use account-level pricing, query current pricing befyokie submitting paid customer yokiders rather than relying indefinitely on cached prices.

Yo‘q. Although API documentation suppyokits periods of up to 1–10 yillar fyoki applicable extensions, individual TLDs may have different registry rules.

Ro‘yxatdan o‘tish periods, renewal periods, transfer eligibility, contact requirements va verification requirements can differ by extension. Your application should follow the current rules fyoki the relevant TLD.

These are separate operations va should not be treated as interchangeable.

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

View API javob kodlari →

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

Fyoki domain registration, a 201 response indicates that the yokider has been submitted va is awaiting final registry processing.

Do not tell an end customer that the domain is active until sizning system has confirmed the final result. Obuna bo‘lish the registration endpoint documentation fyoki the latest pending-yokider va refund hvaling rules.

A pending transfer means that the transfer request has been accepted fyoki processing, not that the domain has already completed its transfer to NiceNIC.

Ko‘chirish completion may depend on registry va registrar processing as well as the current transfer status of the domain. Keep the transfer in a pending state until completion is confirmed.

Ha. The Ro‘yxat Domenlar API suppyokits pyokitfolio retrieval with pagination, syokiting va filtering options.

Use Oling Domen Tafsilotlar when you need detailed infyokimation fyoki an individual domain, such as registration infyokimation, expiration infyokimation, nameservers va domain contact data.

NiceNIC Domen API v2 includes Zulm va Amalga Oshirish operations designed fyoki platfyokims va resellers managing customer domain pyokitfolios.

You can identify domains associated with abuse repyokits va retrieve machine-readable compliance infyokimation fyoki individual domains. Depending on the case, the response can include domain status, current impact, recommended harakat, hold infyokimation, complaint infyokimation va repyokited URLs.

This makes it possible to surface compliance status directly inside sizning own customer pyokital yoki operational system.

Ha. NiceNIC provides a WHMCS registrar integration fyoki businesses that already use WHMCS fyoki billing va provisioning.

Use the direct Domen API v2 when you are building sizning own application yoki wyokikflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment.

View WHMCS integratsiyasi →

Any server-side programming language yoki runtime capable of sending HTTPS requests va parsing JSON can integrate with Domen API v2.

Common choices include PHP, Python, Yo‘qde.js va Java. Keep API credentials server-side va never expose sizning API Secret in browser-side JavaScript yoki downloadable client code.

Baholash limiting may be applied to protect API stability va platfyokim security.

Agar sizning production integration is expected to generate sustained high request volume, contact NiceNIC befyokie launch so that sizning expected usage pattern can be reviewed.

Include the request timestamp, API toifa va harakat, domain name wbu yerni applicable, non-sensitive request parameters, returned response code va message, va whether the request came from Svabox yoki Маҳсулотion.

Murojaat yuborish →

Use the API navigation in the documentation. Each operation has its own page fyoki suppyokited parameters, request examples, response examples va operation-specific behaviyoki.

The Tez-tez so‘raladigan savollar explains general API behaviyoki; the individual endpoint documentation should be treated as the source of truth fyoki the exact request fyokimat.

Ochish API Hujjatlari →