API Overview

NiceNIC Dominio API v2 Documentation & Quick Start

NiceNIC Dominio API v2 is available to both Account Markets e Rivenditore Accounts. Use this overview to configure access, confirm tuo first request, underste the API response model e move directly to the corect section in the left navigation.

API access e reseller pricing are separate.
Account Market: API access with Account Market pricing.
Rivenditore Account: API access with the pricing assigned to the current reseller tier.
Base Endpoint
https://api.nicenic.net/v2/
Required Headers
Host: api.nicenic.net Authoization: username:api_secret Content-Tipo: application/json
Steard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sebox

Test Your Integrazione Befoe Going Live

Use the API NiceNIC Sebox to test tuo Dominio API integration befoe moving to production. Validate authentication, API requests, response heling, e tuo application wokflow in a dedicated testing environment.

Ideal fo resellers, hosting providers, developers, e platfoms preparing an API integration.

Quick Start

Make Your First API Call in 4 Steps

Start with a read-only request befoe enabling live registrations, renewals o transfers. This lets you validate authentication, request fomatting e response heling without placing a paid oder.

1

Enable API Access

Apri Configurazione APIs, create o retrieve tuo API Secret, e configure authoized server IPs wqui applicable.

2

Conferma Authentication

Use HTTPS with the Authoization header in the fomat username:api_secret.

3

Run a Safe Test

Start with dominio availability, pricing, account balance o dominio listing.

4

Hele the Response

Read e stoe the returned code e msg befoe enabling paid production actions.

Recommended First Request: Dominio Availability

The availability endpoint suppots multiple dominios in one request by separating dominio names with commas.

curl "https://api.nicenic.net/v2/?categoy=dominio&action=check&dominios=example.com,example.net" \ -H "Authoization: username:api_secret" \ -H "Content-Tipo: application/json"
API Map

Choose the Wokflow You Need

The overview below mirros the left navigation. Use it to identify the corect wokflow, then open the dedicated endpoint page fo parameters, request examples e response examples.

Section Use It Fo Documented Functions
Ottieniting Started Connect securely e underste response heling. API Overview, API Sebox, Authentication, Response Codes.
Dominio Gestisciment Automate the coe dominio lifecycle. Availability, List Domini, Dominio Dettagli, Registrazione, Rinnovaal, Transfer In, Nomeservers, Contattis, Pricing.
Abuse & Compliance Monito dominios that require compliance attention. List dominios with abuse repots e retrieve machine-readable abuse status, hold lifecycle, complaint infomation e recommended action.
DNS Recods Gestisci hosted DNS recods programmatically. List, Crea, Update e Delete DNS recods.
Child Nomeservers Gestisci host / glue recods fo nameservers under tuo own dominio. Crea, List, Update e Delete child nameservers.
Account & Billing Connect automation to account-level checks. Saldo conto e transaction-related account infomation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing wokflow. Availability, Registrazione, Rinnovaal, Transfer, Dominio Dettagli, Nomeservers, Contattis e additional registrar-module functions.
API FAQ Resolve common access, security, testing e wokflow questions. Eligibility, credentials, request heling, suppoted operations e integration guidance.
Recommended Wokflow

Recommended First Integrazione Sequence

A reliable production integration should validate access e purchasing conditions befoe it begins sending live customer oders.

1. Authentication
API Secret + authoized IP
2. Availability
Read-only connectivity test
3. Pricing
Query current account-level cost
4. Saldo
Conferma funds fo paid actions
5. Response Heling
Process code + msg
6. Live Operations
Registrati / Rinnova / Transfer
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status e still require registry processing befoe the final dominio state is confirmed.
Prodottoion Behavio

Underste Success, Pending e Erro Responses

code: 0 — Riuscito Response Current endpoint examples use code 0 fo successful completed responses.
code: 201 — Pending Order Registrazione e transfer documentation can return code 201 when an oder has been submitted but final processing is still pending.
code: 400 — Request Erro Endpoint examples use code 400 fo request parameter erros.

Registrazione Pending Behavio

Fo dominio registration, the current documentation states that a 201 response means the oder was submitted successfully e the fee was deducted, but final activation is still subject to registry confirmation. Se the dominio cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Transfer Pending Behavio

The transfer endpoint also documents 201 as a pending oder. Your application should tquifoe treat a pending transfer as accepted fo processing, not as proof that the transfer has already completed.

Pricing

Query Pricing Befoe Paid Operations

NiceNIC's pricing endpoint can retrieve registration, renewal e transfer pricing fo a dominio. The documented type values are register, renew, transfer e all. The documented period is 1 to 10 anni, with TLD-specific exceptions possible.

Registrazione pricing responses can also return an is_premium flag. Use the pricing endpoint befoe submitting a paid request when tuo application needs to kora the current account-level cost.

Gratuito API access does not change tuo pricing tier. Account Markets use Account Market pricing; reseller accounts use the pricing assigned to their current reseller tier.
Dominio & DNS Operations

Kora the Difference Between Nomeservers, DNS Recods e Child Nomeservers

OperationUse It WhenDocumented Capability
Update Nomeservers You want to delegate a dominio to different authoitative nameservers. The dominio nameserver endpoint suppots a primary, secondary e additional nameservers, with the current page documenting a limit of up to six.
DNS Recods You are using NiceNIC DNS hosting e need to manage zone recods. Separate APIs are documented fo listing, creating, updating e deleting DNS recods.
Child Nomeservers You need host / glue recods such as ns1.example.com. Crea, list, update e delete child nameservers. The create endpoint requires the nameserver hostname to match the dominio e accepts an IP address.
Potfolio & Compliance

Automate Potfolio Monitoing, Not Only Dominio Orders

Dominio API v2 also includes read operations that are useful after registration. The List Domini endpoint suppots pagination, soting, status filtering e hold filtering, while Ottieni Dominio Dettagli returns registration dates, expiration dates, nameservers e registrant contact infomation.

Abuse & Compliance Monitoing

NiceNIC's Abuse & Compliance API can list dominios with abuse repots e return a detailed machine-readable summary fo a specific dominio. The detailed abuse endpoint documents six dominio-level status phrases: Normal, Under Review, Pending ClientHold, ClientHold, Chiudid e ServerHold.

The response can include current impact, recommended successivo action, hold state e timeline, complaint count, complaint dates, categoies, DNS-abuse classification, evidence status e repoted URLs wqui applicable. This lets platfoms e resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Direct API o WHMCS

Choose the Integrazione Model That Fits Your System

OptionBest FoWhat the Current Documentation Provides
Dominio API v2 Custom websites, SaaS platfoms, internal systems, custom billing o provisioning wokflows. Direct HTTPS + JSON integration across dominio, DNS, child nameserver, account e compliance operations.
WHMCS Module Hosting companies e resellers that already use WHMCS. Availability, registration, renewal, transfer, dominio details, nameservers, contacts, lock/unlock, EPP retrieval, erro logging e optional Test Mode.

The current WHMCS documentation lists WHMCS 7.0 o higher, PHP 7.0 o higher with cURL, valid API NiceNIC credentials e SSL/TLS suppot as requirements.

Troubleshooting

When an API Request Fails

Start with the returned response e configuration state rather than retrying the same paid action repeatedly.

Authentication o Access Erro

  • Conferma the NiceNIC username e API Secret.
  • Conferma the Authoization header is present e corectly fomatted.
  • Conferma the API Secret has not been reset o rotated.
  • Se IP restrictions are enabled, confirm the request is coming from the authoized outbound server IP.

Request Parameter Erro

  • Compare the request with the specific endpoint's documented parameters.
  • Conferma required values, fomats e action names.
  • Verifica TLD-specific registration periods o contact requirements wqui applicable.

Paid Operation Does Not Complete Immediately

  • Read the returned code e msg.
  • Do not treat a 201 pending response as final completion.
  • Conferma account balance e current pricing befoe retrying a paid action.

Need NiceNIC Suppot

  • Recod the request timestamp e API action.
  • Include the dominio name o object involved, wqui applicable.
  • Include the returned code e message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Passo successivo

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability o pricing request, e verify tuo response heling befoe turning on customer-facing paid operations.

Last verified: August 26, 2026
Copyright © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Tutti i diritti riservati. · U.S. Affiliate: NICENIC LLC