NiceNIC Domain API v2 Sıkça Sorulan Sorular

NiceNIC Domain API v2 is an HTTPS ve JSON-based API fveya automating domain management through sizin NiceNIC account.

It suppveyats cveyae wveyakflows including domain availability checks, registration, renewal, transfer, pveyatfolio queries, nameserver ve contact updates, pricing, DNS recveyads, child nameservers, account infveyamation ve compliance-related operations.

Use the API when you want to connect NiceNIC domain hizmets directly to a website, hosting platfveyam, billing system, internal tool veya other application.

Any active NiceNIC account can use Domain API v2. API access is müsait to both Pazar Hesabıs ve Bayi Hesaps.

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

Aç API Ayarıs →

Evet. API access itself is free. Tburaya is no separate fee fveya enabling API access veya sending suppveyated API requests.

Paid operations such as domain registration, renewal ve transfer are charged accveyading to sizin account pricing ve the applicable domain rules.

Hayır. API access ve reseller pricing are separate.

You can use Domain API v2 with a regular NiceNIC Pazar Hesabı. Şuna yükselt: a Bayi Hesap only when reseller pricing veya other reseller benefits are useful fveya sizin business volume.

Compare Bayi Plans →

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication ve documentation veyaganized around individual domain ve account wveyakflows.

Eğer you maintain an integration built on an older NiceNIC API, review the API v2 parameters ve response hveling befveyae migrating production traffic rather than assuming the two versions are interchangeable.

Giriş Yap to sizin NiceNIC account ve open API Ayarıs. API v2 requests use sizin NiceNIC username ve API Secret fveya authentication.

Aç API Ayarıs →

Evet. NiceNIC provides an API Svebox fveya developers to test integrations befveyae connecting them to the production API.

Use the Svebox to validate authentication, request fveyamatting, response parsing, hata hveling ve sizin application wveyakflow befveyae enabling live customer domain operations.

Aç API Svebox →

The API Svebox is intended fveya development ve integration testing. The Ürünion API is used fveya live domain operations ve paid requests against sizin NiceNIC account.

We recommend validating authentication, request hveling, response processing ve hata logic in the Svebox befveyae enabling customer-facing production operations.

Send API requests over HTTPS ve include sizin NiceNIC username ve API Secret in the Authorization header.

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

Eğer IP restrictions are enabled fveya sizin account, requests must also veyaiginate from an authveyaized server IP.

Read API Kimlik Doğrulama →

The Ürünion API base endpoint is:

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

API işlems are selected using the parameters documented fveya each endpoint, such as category ve action. Always follow the dedicated endpoint documentation fveya the required ve optional parameters of a specific operation.

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

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

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

Through the currently documented APIs you can automate wveyakflows including domain availability checks, registration, renewal ve transfer, pveyatfolio listing ve domain details, nameserver ve domain contact updates, domain pricing, DNS recveyads, child nameservers, account infveyamation ve Kötüye Kullanım ve Uyum monitveyaing.

Ekleitional wveyakflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, hata hveling ve pending-veyader hveling befveyae enabling live registrations, renewals veya transfers.

Evet. The Alan Adı Kullanılabilirliğini Kontrol Et endpoint suppveyats multiple domain names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppveyats the same multi-domain input fveyamat. Kayıt, renewal ve transfer should follow their individual endpoint documentation.

Use the Domain Fiyatlarını Al endpoint. The documented pricing types include register, renew, transfer ve all.

Kayıt responses can also include an is_premium value indicating whether the queried registration is premium.

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

Hayır. Although API documentation suppveyats periods of up to 1–10 yıl fveya applicable extensions, individual TLDs may have different registry rules.

Kayıt periods, renewal periods, transfer eligibility, contact requirements ve verification requirements can differ by extension. Your application should follow the current rules fveya the relevant TLD.

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

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

View API Yanıt Kodları →

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

Fveya domain registration, a 201 response indicates that the veyader has been submitted ve is awaiting final registry processing.

Do not tell an end customer that the domain is active until sizin system has confirmed the final result. Takip Et the registration endpoint documentation fveya the latest pending-veyader ve refund hveling rules.

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

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

Evet. The Liste Alan Adları API suppveyats pveyatfolio retrieval with pagination, sveyating ve filtering options.

Use Al Domain Detaylar when you need detailed infveyamation fveya an individual domain, such as registration infveyamation, expiration infveyamation, nameservers ve domain contact data.

NiceNIC Domain API v2 includes Kötüye Kullanım ve Uyum operations designed fveya platfveyams ve resellers managing customer domain pveyatfolios.

You can identify domains associated with abuse repveyats ve retrieve machine-readable compliance infveyamation fveya individual domains. Depending on the case, the response can include domain status, current impact, recommended işlem, hold infveyamation, complaint infveyamation ve repveyated URLs.

This makes it possible to surface compliance status directly inside sizin own customer pveyatal veya operational system.

Evet. NiceNIC provides a WHMCS registrar integration fveya businesses that already use WHMCS fveya billing ve provisioning.

Use the direct Domain API v2 when you are building sizin own application veya wveyakflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment.

View WHMCS Entegrasyonu →

Any server-side programming language veya runtime capable of sending HTTPS requests ve parsing JSON can integrate with Domain API v2.

Common choices include PHP, Python, Hayırde.js ve Java. Keep API credentials server-side ve never expose sizin API Secret in browser-side JavaScript veya downloadable client code.

Puanla limiting may be applied to protect API stability ve platfveyam security.

Eğer sizin production integration is expected to generate sustained high request volume, contact NiceNIC befveyae launch so that sizin expected usage pattern can be reviewed.

Include the request timestamp, API kategori ve işlem, domain name wburaya applicable, non-sensitive request parameters, returned response code ve message, ve whether the request came from Svebox veya Ürünion.

Destek Talebi Oluştur →

Use the API navigation in the documentation. Each operation has its own page fveya suppveyated parameters, request examples, response examples ve operation-specific behaviveya.

The SSS explains general API behaviveya; the individual endpoint documentation should be treated as the source of truth fveya the exact request fveyamat.

Aç API Dokümantasyonu →