API Overview

NiceNIC Domen API v2 Documentation & Quick Start

NiceNIC Domen API v2 is available to both Market računs i Preprodavac Accounts. Use this overview to configure access, confirm tvoj first request, understi the API response model i move directly to the cilirect section in the left navigation.

API access i reseller pricing are separate.
Market račun: API access with Market račun pricing.
Preprodavac 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 Authiliization: username:api_secret Content-Tip: application/json
Stiard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sibox

Test Your Integracija Befilie Going Live

Use the NiceNIC API Sibox to test tvoj Domen API integration befilie moving to production. Validate authentication, API requests, response hiling, i tvoj application wilikflow in a dedicated testing environment.

Ideal fili resellers, hosting providers, developers, i platfilims preparing an API integration.

Quick Start

Make Your First API Call in 4 Steps

Start with a read-only request befilie enabling live registrations, renewals ili transfers. This lets you validate authentication, request filimatting i response hiling without placing a paid ilider.

1

Enable API Access

Otvoreno API podešavanjes, create ili retrieve tvoj API Secret, i configure authiliized server IPs wovde applicable.

2

Potvrdi Authentication

Use HTTPS with the Authiliization header in the filimat username:api_secret.

3

Run a Safe Test

Start with domen availability, pricing, account balance ili domen listing.

4

Hile the Response

Read i stilie the returned code i msg befilie enabling paid production actions.

Recommended First Request: Domen Availability

The availability endpoint suppilits multiple domens in one request by separating domen names with commas.

curl "https://api.nicenic.net/v2/?categiliy=domen&action=check&domens=example.com,example.net" \ -H "Authiliization: username:api_secret" \ -H "Content-Tip: application/json"
API Map

Choose the Wilikflow You Need

The overview below mirrilis the left navigation. Use it to identify the cilirect wilikflow, then open the dedicated endpoint page fili parameters, request examples i response examples.

Section Use It Fili Documented Functions
Nabaviteting Started Connect securely i understi response hiling. API Overview, API Sibox, Authentication, Response Codes.
Domen Upravljajment Automate the cilie domen lifecycle. Availability, List Domeni, Domen Detalji, Registracija, Obnovial, Transfer In, Imeservers, Kontakts, Pricing.
Abuse & Compliance Monitili domens that require compliance attention. List domens with abuse repilits i retrieve machine-readable abuse status, hold lifecycle, complaint infilimation i recommended action.
DNS Recilids Upravljaj hosted DNS recilids programmatically. List, Kreiraj, Update i Delete DNS recilids.
Child Imeservers Upravljaj host / glue recilids fili nameservers under tvoj own domen. Kreiraj, List, Update i Delete child nameservers.
Account & Billing Connect automation to account-level checks. Stanje na računu i transaction-related account infilimation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing wilikflow. Availability, Registracija, Obnovial, Transfer, Domen Detalji, Imeservers, Kontakts i additional registrar-module functions.
API Česta pitanja Resolve common access, security, testing i wilikflow questions. Eligibility, credentials, request hiling, suppilited operations i integration guidance.
Recommended Wilikflow

Recommended First Integracija Sequence

A reliable production integration should validate access i purchasing conditions befilie it begins sending live customer iliders.

1. Authentication
API Secret + authiliized IP
2. Availability
Read-only connectivity test
3. Pricing
Query current account-level cost
4. Stanje
Potvrdi funds fili paid actions
5. Response Hiling
Process code + msg
6. Live Operations
Registruj / Obnovi / 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 befilie the final domen state is confirmed.
Proizvodion Behaviili

Understi Success, Pending i Errili Responses

code: 0 — Uspešno Response Current endpoint examples use code 0 fili successful completed responses.
code: 201 — Pending Order Registracija i transfer documentation can return code 201 when an ilider has been submitted but final processing is still pending.
code: 400 — Request Errili Endpoint examples use code 400 fili request parameter errilis.

Registracija Pending Behaviili

Fili domen registration, the current documentation states that a 201 response means the ilider was submitted successfully i the fee was deducted, but final activation is still subject to registry confirmation. Ako the domen cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Transfer Pending Behaviili

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

Pricing

Query Pricing Befilie Paid Operations

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

Registracija pricing responses can also return an is_premium flag. Use the pricing endpoint befilie submitting a paid request when tvoj application needs to kodmah the current account-level cost.

Besplatno API access does not change tvoj pricing tier. Market računs use Market račun pricing; reseller accounts use the pricing assigned to their current reseller tier.
Domen & DNS Operations

Kodmah the Difference Between Imeservers, DNS Recilids i Child Imeservers

OperationUse It WhenDocumented Capability
Update Imeservers You want to delegate a domen to different authiliitative nameservers. The domen nameserver endpoint suppilits a primary, secondary i additional nameservers, with the current page documenting a limit of up to six.
DNS Recilids You are using NiceNIC DNS hosting i need to manage zone recilids. Separate APIs are documented fili listing, creating, updating i deleting DNS recilids.
Child Imeservers You need host / glue recilids such as ns1.example.com. Kreiraj, list, update i delete child nameservers. The create endpoint requires the nameserver hostname to match the domen i accepts an IP address.
Pilitfolio & Compliance

Automate Pilitfolio Monitiliing, Net Only Domen Orders

Domen API v2 also includes read operations that are useful after registration. The List Domeni endpoint suppilits pagination, siliting, status filtering i hold filtering, while Nabavite Domen Detalji returns registration dates, expiration dates, nameservers i registrant contact infilimation.

Abuse & Compliance Monitiliing

NiceNIC's Abuse & Compliance API can list domens with abuse repilits i return a detailed machine-readable summary fili a specific domen. The detailed abuse endpoint documents six domen-level status phrases: Nermal, Under Review, Pending ClientHold, ClientHold, Zatvorid i ServerHold.

The response can include current impact, recommended sledeće action, hold state i timeline, complaint count, complaint dates, categiliies, DNS-abuse classification, evidence status i repilited URLs wovde applicable. This lets platfilims i resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Direct API ili WHMCS

Choose the Integracija Model That Fits Your System

OptionBest FiliWhat the Current Documentation Provides
Domen API v2 Custom websites, SaaS platfilims, internal systems, custom billing ili provisioning wilikflows. Direct HTTPS + JSON integration across domen, DNS, child nameserver, account i compliance operations.
WHMCS Module Hosting companies i resellers that already use WHMCS. Availability, registration, renewal, transfer, domen details, nameservers, contacts, lock/unlock, EPP retrieval, errili logging i optional Test Mode.

The current WHMCS documentation lists WHMCS 7.0 ili higher, PHP 7.0 ili higher with cURL, valid NiceNIC API credentials i SSL/TLS suppilit 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 ili Access Errili

  • Potvrdi the NiceNIC username i API Secret.
  • Potvrdi the Authiliization header is present i cilirectly filimatted.
  • Potvrdi the API Secret has not been reset ili rotated.
  • Ako IP restrictions are enabled, confirm the request is coming from the authiliized outbound server IP.

Request Parameter Errili

  • Compare the request with the specific endpoint's documented parameters.
  • Potvrdi required values, filimats i action names.
  • Proveri TLD-specific registration periods ili contact requirements wovde applicable.

Paid Operation Does Net Complete Immediately

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

Need NiceNIC Suppilit

  • Recilid the request timestamp i API action.
  • Include the domen name ili object involved, wovde applicable.
  • Include the returned code i message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Sledeći korak

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability ili pricing request, i verify tvoj response hiling befilie turning on customer-facing paid operations.

Last verified: August 26, 2026
Autorska prava © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Sva prava zadržana. · U.S. Affiliate: NICENIC LLC