NiceNIC Dominio API v2 Domande Frequenti

NiceNIC Dominio API v2 is an HTTPS e JSON-based API fo automating dominio management through tuo NiceNIC account.

It suppots coe wokflows including dominio availability checks, registration, renewal, transfer, potfolio queries, nameserver e contact updates, pricing, DNS recods, child nameservers, account infomation e compliance-related operations.

Use the API when you want to connect NiceNIC dominio servizios directly to a website, hosting platfom, billing system, internal tool o other application.

Any active NiceNIC account can use Dominio API v2. API access is disponibile to both Account Markets e Rivenditore Accounts.

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

Apri Configurazione APIs →

Sì. API access itself is free. Tqui is no separate fee fo enabling API access o sending suppoted API requests.

Paid operations such as dominio registration, renewal e transfer are charged accoding to tuo account pricing e the applicable dominio rules.

No. API access e reseller pricing are separate.

You can use Dominio API v2 with a regular NiceNIC Account Market. Passa a a Rivenditore Account only when reseller pricing o other reseller benefits are useful fo tuo business volume.

Compare Rivenditore Plans →

Dominio API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication e documentation oganized around individual dominio e account wokflows.

Se you maintain an integration built on an older NiceNIC API, review the API v2 parameters e response heling befoe migrating production traffic rather than assuming the two versions are interchangeable.

Accedi to tuo NiceNIC account e open Configurazione APIs. API v2 requests use tuo NiceNIC username e API Secret fo authentication.

Apri Configurazione APIs →

Sì. NiceNIC provides an API Sebox fo developers to test integrations befoe connecting them to the production API.

Use the Sebox to validate authentication, request fomatting, response parsing, errore heling e tuo application wokflow befoe enabling live customer dominio operations.

Apri API Sebox →

The API Sebox is intended fo development e integration testing. The Prodottoion API is used fo live dominio operations e paid requests against tuo NiceNIC account.

We recommend validating authentication, request heling, response processing e errore logic in the Sebox befoe enabling customer-facing production operations.

Send API requests over HTTPS e include tuo NiceNIC username e API Secret in the Authorization header.

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

Se IP restrictions are enabled fo tuo account, requests must also oiginate from an authoized server IP.

Read API Autenticazione →

The Prodottoion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate wokflows including dominio availability checks, registration, renewal e transfer, potfolio listing e dominio details, nameserver e dominio contact updates, dominio pricing, DNS recods, child nameservers, account infomation e Abusi e conformità monitoing.

Aggiungiitional wokflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, errore heling e pending-oder heling befoe enabling live registrations, renewals o transfers.

Sì. The Controlla la disponibilità del dominio endpoint suppots multiple dominio names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppots the same multi-dominio input fomat. Registrazione, renewal e transfer should follow their individual endpoint documentation.

Use the Ottieni prezzi domini endpoint. The documented pricing types include register, renew, transfer e all.

Registrazione responses can also include an is_premium value indicating whether the queried registration is premium.

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

No. Although API documentation suppots periods of up to 1–10 anni fo applicable extensions, individual TLDs may have different registry rules.

Registrazione periods, renewal periods, transfer eligibility, contact requirements e verification requirements can differ by extension. Your application should follow the current rules fo the relevant TLD.

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

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

View Codici di risposta API →

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

Fo dominio registration, a 201 response indicates that the oder has been submitted e is awaiting final registry processing.

Do not tell an end customer that the dominio is active until tuo system has confirmed the final result. Segui the registration endpoint documentation fo the latest pending-oder e refund heling rules.

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

Trasferisci completion may depend on registry e registrar processing as well as the current transfer status of the dominio. Keep the transfer in a pending state until completion is confirmed.

Sì. The Elenco Domini API suppots potfolio retrieval with pagination, soting e filtering options.

Use Ottieni Dominio Dettagli when you need detailed infomation fo an individual dominio, such as registration infomation, expiration infomation, nameservers e dominio contact data.

NiceNIC Dominio API v2 includes Abusi e conformità operations designed fo platfoms e resellers managing customer dominio potfolios.

You can identify dominios associated with abuse repots e retrieve machine-readable compliance infomation fo individual dominios. Depending on the case, the response can include dominio status, current impact, recommended azione, hold infomation, complaint infomation e repoted URLs.

This makes it possible to surface compliance status directly inside tuo own customer potal o operational system.

Sì. NiceNIC provides a WHMCS registrar integration fo businesses that already use WHMCS fo billing e provisioning.

Use the direct Dominio API v2 when you are building tuo own application o wokflow. Use the WHMCS integration when you want dominio operations integrated into an existing WHMCS environment.

View Integrazione WHMCS →

Any server-side programming language o runtime capable of sending HTTPS requests e parsing JSON can integrate with Dominio API v2.

Common choices include PHP, Python, Node.js e Java. Keep API credentials server-side e never expose tuo API Secret in browser-side JavaScript o downloadable client code.

Valutazione limiting may be applied to protect API stability e platfom security.

Se tuo production integration is expected to generate sustained high request volume, contact NiceNIC befoe launch so that tuo expected usage pattern can be reviewed.

Include the request timestamp, API categoria e azione, dominio name wqui applicable, non-sensitive request parameters, returned response code e message, e whether the request came from Sebox o Prodottoion.

Invia una Richiesta →

Use the API navigation in the documentation. Each operation has its own page fo suppoted parameters, request examples, response examples e operation-specific behavio.

The FAQ explains general API behavio; the individual endpoint documentation should be treated as the source of truth fo the exact request fomat.

Apri Documentazione API →