API Overview

NiceNIC Domini API v2 Documentation & Quick Start

NiceNIC Domini API v2 is available to both Compte de mercats i Revendedor Accounts. Use this overview to configure access, confirm el teu first request, understi the API response model i move directly to the corect section in the left navigation.

API access i reseller pricing are separate.
Compte de mercat: API access with Compte de mercat pricing.
Revendedor 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-Tipus: application/json
Stiard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sibox

Test Your Integració Befoe Going Live

Use the NiceNIC API Sibox to test el teu Domini API integration befoe moving to production. Validate authentication, API requests, response hiling, i el teu application wokflow in a dedicated testing environment.

Ideal fo resellers, hosting providers, developers, i 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 i response hiling without placing a paid oder.

1

Enable API Access

Obert Configuració APIs, create o retrieve el teu API Secret, i configure authoized server IPs waquí applicable.

2

Confirma Authentication

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

3

Run a Safe Test

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

4

Hile the Response

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

Recommended First Request: Domini Availability

The availability endpoint suppots multiple dominis in one request by separating domini names with commas.

curl "https://api.nicenic.net/v2/?categoy=domini&action=check&dominis=example.com,example.net" \ -H "Authoization: username:api_secret" \ -H "Content-Tipus: 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 i response examples.

Section Use It Fo Documented Functions
Obtenirting Started Connect securely i understi response hiling. API Overview, API Sibox, Authentication, Response Codes.
Domini Gestionarment Automate the coe domini lifecycle. Availability, List Dominis, Domini Detalls, Registre, Renovaral, Transfer In, Nomservers, Contactes, Pricing.
Abuse & Compliance Monito dominis that require compliance attention. List dominis with abuse repots i retrieve machine-readable abuse status, hold lifecycle, complaint infomation i recommended action.
DNS Recods Gestionar hosted DNS recods programmatically. List, Crear, Update i Delete DNS recods.
Child Nomservers Gestionar host / glue recods fo nameservers under el teu own domini. Crear, List, Update i Delete child nameservers.
Account & Billing Connect automation to account-level checks. Saldo del compte i transaction-related account infomation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing wokflow. Availability, Registre, Renovaral, Transfer, Domini Detalls, Nomservers, Contactes i additional registrar-module functions.
API Preguntes freqüents Resolve common access, security, testing i wokflow questions. Eligibility, credentials, request hiling, suppoted operations i integration guidance.
Recommended Wokflow

Recommended First Integració Sequence

A reliable production integration should validate access i 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
Confirma funds fo paid actions
5. Response Hiling
Process code + msg
6. Live Operations
Registrar / Renovar / Transfer
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status i still require registry processing befoe the final domini state is confirmed.
Producteion Behavio

Understi Success, Pending i Erro Responses

code: 0 — Amb èxit Response Current endpoint examples use code 0 fo successful completed responses.
code: 201 — Pending Order Registre i 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.

Registre Pending Behavio

Fo domini registration, the current documentation states that a 201 response means the oder was submitted successfully i the fee was deducted, but final activation is still subject to registry confirmation. Si the domini 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 taquífoe 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 i transfer pricing fo a domini. The documented type values are register, renew, transfer i all. The documented period is 1 to 10 anys, with TLD-specific exceptions possible.

Registre pricing responses can also return an is_premium flag. Use the pricing endpoint befoe submitting a paid request when el teu application needs to kara the current account-level cost.

Gratuït API access does not change el teu pricing tier. Compte de mercats use Compte de mercat pricing; reseller accounts use the pricing assigned to their current reseller tier.
Domini & DNS Operations

Kara the Difference Between Nomservers, DNS Recods i Child Nomservers

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

Automate Potfolio Monitoing, Not Only Domini Orders

Domini API v2 also includes read operations that are useful after registration. The List Dominis endpoint suppots pagination, soting, status filtering i hold filtering, while Obtenir Domini Detalls returns registration dates, expiration dates, nameservers i registrant contact infomation.

Abuse & Compliance Monitoing

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

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

Direct API o WHMCS

Choose the Integració Model That Fits Your System

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

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

Troubleshooting

When an API Request Fails

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

Authentication o Access Erro

  • Confirma the NiceNIC username i API Secret.
  • Confirma the Authoization header is present i corectly fomatted.
  • Confirma the API Secret has not been reset o rotated.
  • Si 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.
  • Confirma required values, fomats i action names.
  • Comprovar TLD-specific registration periods o contact requirements waquí applicable.

Paid Operation Does Not Complete Immediately

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

Need NiceNIC Suppot

  • Recod the request timestamp i API action.
  • Include the domini name o object involved, waquí applicable.
  • Include the returned code i message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Següent pas

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability o pricing request, i verify el teu response hiling befoe turning on customer-facing paid operations.

Last verified: August 26, 2026
Drets d'autor © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Tots els drets reservats. · U.S. Affiliate: NICENIC LLC