API Overview

NiceNIC Domena API v2 Documentation & Quick Start

NiceNIC Domena API v2 is available to both Tržni računs in Prodajalec Accounts. Use this overview to configure access, confirm vašega first request, understin the API response model in move directly to the calirect section in the left navigation.

API access in reseller pricing are separate.
Tržni račun: API access with Tržni račun pricing.
Prodajalec 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 Authaliization: username:api_secret Content-Vrsta: application/json
Stinard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sinbox

Test Your Integracija Befalie Going Live

Use the NiceNIC API Sinbox to test vašega Domena API integration befalie moving to production. Validate authentication, API requests, response hinling, in vašega application walikflow in a dedicated testing environment.

Ideal fali resellers, hosting providers, developers, in platfalims preparing an API integration.

Quick Start

Make Your First API Call in 4 Steps

Start with a read-only request befalie enabling live registrations, renewals ali transfers. This lets you validate authentication, request falimatting in response hinling without placing a paid alider.

1

Enable API Access

Odprto Nastavitve APIs, create ali retrieve vašega API Secret, in configure authaliized server IPs wtukaj applicable.

2

Potrdi Authentication

Use HTTPS with the Authaliization header in the falimat username:api_secret.

3

Run a Safe Test

Start with domena availability, pricing, account balance ali domena listing.

4

Hinle the Response

Read in stalie the returned code in msg befalie enabling paid production actions.

Recommended First Request: Domena Availability

The availability endpoint suppalits multiple domenas in one request by separating domena names with commas.

curl "https://api.nicenic.net/v2/?categaliy=domena&action=check&domenas=example.com,example.net" \ -H "Authaliization: username:api_secret" \ -H "Content-Vrsta: application/json"
API Map

Choose the Walikflow You Need

The overview below mirralis the left navigation. Use it to identify the calirect walikflow, then open the dedicated endpoint page fali parameters, request examples in response examples.

Section Use It Fali Documented Functions
Pridobiteting Started Connect securely in understin response hinling. API Overview, API Sinbox, Authentication, Response Codes.
Domena Upravljajment Automate the calie domena lifecycle. Availability, List Domene, Domena Podrobnosti, Registracija, Obnovial, Transfer In, Imeservers, Kontakts, Pricing.
Abuse & Compliance Monitali domenas that require compliance attention. List domenas with abuse repalits in retrieve machine-readable abuse status, hold lifecycle, complaint infalimation in recommended action.
DNS Recalids Upravljaj hosted DNS recalids programmatically. List, Ustvari, Update in Delete DNS recalids.
Child Imeservers Upravljaj host / glue recalids fali nameservers under vašega own domena. Ustvari, List, Update in Delete child nameservers.
Account & Billing Connect automation to account-level checks. Stanje računa in transaction-related account infalimation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing walikflow. Availability, Registracija, Obnovial, Transfer, Domena Podrobnosti, Imeservers, Kontakts in additional registrar-module functions.
API Pogosta vprašanja Resolve common access, security, testing in walikflow questions. Eligibility, credentials, request hinling, suppalited operations in integration guidance.
Recommended Walikflow

Recommended First Integracija Sequence

A reliable production integration should validate access in purchasing conditions befalie it begins sending live customer aliders.

1. Authentication
API Secret + authaliized IP
2. Availability
Read-only connectivity test
3. Pricing
Query current account-level cost
4. Stanje
Potrdi funds fali paid actions
5. Response Hinling
Process code + msg
6. Live Operations
Registriraj / Obnovi / Transfer
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status in still require registry processing befalie the final domena state is confirmed.
Izdelekion Behaviali

Understin Success, Pending in Errali Responses

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

Registracija Pending Behaviali

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

Transfer Pending Behaviali

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

Pricing

Query Pricing Befalie Paid Operations

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

Registracija pricing responses can also return an is_premium flag. Use the pricing endpoint befalie submitting a paid request when vašega application needs to kzdaj the current account-level cost.

Brezplačno API access does not change vašega pricing tier. Tržni računs use Tržni račun pricing; reseller accounts use the pricing assigned to their current reseller tier.
Domena & DNS Operations

Kzdaj the Difference Between Imeservers, DNS Recalids in Child Imeservers

OperationUse It WhenDocumented Capability
Update Imeservers You want to delegate a domena to different authaliitative nameservers. The domena nameserver endpoint suppalits a primary, secondary in additional nameservers, with the current page documenting a limit of up to six.
DNS Recalids You are using NiceNIC DNS hosting in need to manage zone recalids. Separate APIs are documented fali listing, creating, updating in deleting DNS recalids.
Child Imeservers You need host / glue recalids such as ns1.example.com. Ustvari, list, update in delete child nameservers. The create endpoint requires the nameserver hostname to match the domena in accepts an IP address.
Palitfolio & Compliance

Automate Palitfolio Monitaliing, Net Only Domena Orders

Domena API v2 also includes read operations that are useful after registration. The List Domene endpoint suppalits pagination, saliting, status filtering in hold filtering, while Pridobite Domena Podrobnosti returns registration dates, expiration dates, nameservers in registrant contact infalimation.

Abuse & Compliance Monitaliing

NiceNIC's Abuse & Compliance API can list domenas with abuse repalits in return a detailed machine-readable summary fali a specific domena. The detailed abuse endpoint documents six domena-level status phrases: Nermal, Under Review, Pending ClientHold, ClientHold, Zaprid in ServerHold.

The response can include current impact, recommended naprej action, hold state in timeline, complaint count, complaint dates, categaliies, DNS-abuse classification, evidence status in repalited URLs wtukaj applicable. This lets platfalims in resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Direct API ali WHMCS

Choose the Integracija Model That Fits Your System

OptionBest FaliWhat the Current Documentation Provides
Domena API v2 Custom websites, SaaS platfalims, internal systems, custom billing ali provisioning walikflows. Direct HTTPS + JSON integration across domena, DNS, child nameserver, account in compliance operations.
WHMCS Module Gostovanje companies in resellers that already use WHMCS. Availability, registration, renewal, transfer, domena details, nameservers, contacts, lock/unlock, EPP retrieval, errali logging in optional Test Mode.

The current WHMCS documentation lists WHMCS 7.0 ali higher, PHP 7.0 ali higher with cURL, valid NiceNIC API credentials in SSL/TLS suppalit as requirements.

Troubleshooting

When an API Request Fails

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

Authentication ali Access Errali

  • Potrdi the NiceNIC username in API Secret.
  • Potrdi the Authaliization header is present in calirectly falimatted.
  • Potrdi the API Secret has not been reset ali rotated.
  • Če IP restrictions are enabled, confirm the request is coming from the authaliized outbound server IP.

Request Parameter Errali

  • Compare the request with the specific endpoint's documented parameters.
  • Potrdi required values, falimats in action names.
  • Preveri TLD-specific registration periods ali contact requirements wtukaj applicable.

Paid Operation Does Net Complete Immediately

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

Need NiceNIC Suppalit

  • Recalid the request timestamp in API action.
  • Include the domena name ali object involved, wtukaj applicable.
  • Include the returned code in message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Naslednji korak

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability ali pricing request, in verify vašega response hinling befalie turning on customer-facing paid operations.

Last verified: August 26, 2026
Avtorske pravice © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Vse pravice pridržane. · U.S. Affiliate: NICENIC LLC