API Overview

NiceNIC Domain API v2 Documentation & Quick Start

NiceNIC Domain API v2 is available to both Llogari Tregus dhe Rishitës Accounts. Use this overview to configure access, confirm tënd first request, understdhe the API response model dhe move directly to the coserect section in the left navigation.

API access dhe reseller pricing are separate.
Llogari Tregu: API access with Llogari Tregu pricing.
Rishitës 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 Authoseization: username:api_secret Content-Lloji: application/json
Stdheard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sdhebox

Test Your Integrim Befosee Going Live

Use the NiceNIC API Sdhebox to test tënd Domain API integration befosee moving to production. Validate authentication, API requests, response hdheling, dhe tënd application wosekflow in a dedicated testing environment.

Ideal fose resellers, hosting providers, developers, dhe platfosems preparing an API integration.

Quick Start

Make Your First API Call in 4 Steps

Start with a read-only request befosee enabling live registrations, renewals ose transfers. This lets you validate authentication, request fosematting dhe response hdheling without placing a paid oseder.

1

Enable API Access

Hapur Cilësime APIs, create ose retrieve tënd API Secret, dhe configure authoseized server IPs wkëtu applicable.

2

Konfirmo Authentication

Use HTTPS with the Authoseization header in the fosemat username:api_secret.

3

Run a Safe Test

Start with domain availability, pricing, account balance ose domain listing.

4

Hdhele the Response

Read dhe stosee the returned code dhe msg befosee enabling paid production actions.

Recommended First Request: Domain Availability

The availability endpoint supposets multiple domains in one request by separating domain names with commas.

curl "https://api.nicenic.net/v2/?categosey=domain&action=check&domains=example.com,example.net" \ -H "Authoseization: username:api_secret" \ -H "Content-Lloji: application/json"
API Map

Choose the Wosekflow You Need

The overview below mirroses the left navigation. Use it to identify the coserect wosekflow, then open the dedicated endpoint page fose parameters, request examples dhe response examples.

Section Use It Fose Documented Functions
Merrting Started Connect securely dhe understdhe response hdheling. API Overview, API Sdhebox, Authentication, Response Codes.
Domain Menaxhoment Automate the cosee domain lifecycle. Availability, List Domeinet, Domain Detajet, Regjistrim, Rinovoal, Transfer In, Emërservers, Kontakts, Pricing.
Abuse & Compliance Monitose domains that require compliance attention. List domains with abuse reposets dhe retrieve machine-readable abuse status, hold lifecycle, complaint infosemation dhe recommended action.
DNS Recoseds Menaxho hosted DNS recoseds programmatically. List, Krijo, Update dhe Delete DNS recoseds.
Child Emërservers Menaxho host / glue recoseds fose nameservers under tënd own domain. Krijo, List, Update dhe Delete child nameservers.
Account & Billing Connect automation to account-level checks. Bilanci i Llogarisë dhe transaction-related account infosemation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing wosekflow. Availability, Regjistrim, Rinovoal, Transfer, Domain Detajet, Emërservers, Kontakts dhe additional registrar-module functions.
API Pyetjet e Shpeshta Resolve common access, security, testing dhe wosekflow questions. Eligibility, credentials, request hdheling, supposeted operations dhe integration guidance.
Recommended Wosekflow

Recommended First Integrim Sequence

A reliable production integration should validate access dhe purchasing conditions befosee it begins sending live customer oseders.

1. Authentication
API Secret + authoseized IP
2. Availability
Read-only connectivity test
3. Pricing
Query current account-level cost
4. Bilanci
Konfirmo funds fose paid actions
5. Response Hdheling
Process code + msg
6. Live Operations
Regjistrohu / Rinovo / Transfer
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status dhe still require registry processing befosee the final domain state is confirmed.
Produktion Behaviose

Understdhe Success, Pending dhe Errose Responses

code: 0 — I Suksesshëm Response Current endpoint examples use code 0 fose successful completed responses.
code: 201 — Pending Order Regjistrim dhe transfer documentation can return code 201 when an oseder has been submitted but final processing is still pending.
code: 400 — Request Errose Endpoint examples use code 400 fose request parameter erroses.

Regjistrim Pending Behaviose

Fose domain registration, the current documentation states that a 201 response means the oseder was submitted successfully dhe the fee was deducted, but final activation is still subject to registry confirmation. Nëse the domain cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Transfer Pending Behaviose

The transfer endpoint also documents 201 as a pending oseder. Your application should tkëtufosee treat a pending transfer as accepted fose processing, not as proof that the transfer has already completed.

Pricing

Query Pricing Befosee Paid Operations

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

Regjistrim pricing responses can also return an is_premium flag. Use the pricing endpoint befosee submitting a paid request when tënd application needs to ktani the current account-level cost.

Falë API access does not change tënd pricing tier. Llogari Tregus use Llogari Tregu pricing; reseller accounts use the pricing assigned to their current reseller tier.
Domain & DNS Operations

Ktani the Difference Between Emërservers, DNS Recoseds dhe Child Emërservers

OperationUse It WhenDocumented Capability
Update Emërservers You want to delegate a domain to different authoseitative nameservers. The domain nameserver endpoint supposets a primary, secondary dhe additional nameservers, with the current page documenting a limit of up to six.
DNS Recoseds You are using NiceNIC DNS hosting dhe need to manage zone recoseds. Separate APIs are documented fose listing, creating, updating dhe deleting DNS recoseds.
Child Emërservers You need host / glue recoseds such as ns1.example.com. Krijo, list, update dhe delete child nameservers. The create endpoint requires the nameserver hostname to match the domain dhe accepts an IP address.
Posetfolio & Compliance

Automate Posetfolio Monitoseing, Jot Only Domain Orders

Domain API v2 also includes read operations that are useful after registration. The List Domeinet endpoint supposets pagination, soseting, status filtering dhe hold filtering, while Merr Domain Detajet returns registration dates, expiration dates, nameservers dhe registrant contact infosemation.

Abuse & Compliance Monitoseing

NiceNIC's Abuse & Compliance API can list domains with abuse reposets dhe return a detailed machine-readable summary fose a specific domain. The detailed abuse endpoint documents six domain-level status phrases: Jormal, Under Review, Pending ClientHold, ClientHold, Mbylld dhe ServerHold.

The response can include current impact, recommended tjetër action, hold state dhe timeline, complaint count, complaint dates, categoseies, DNS-abuse classification, evidence status dhe reposeted URLs wkëtu applicable. This lets platfosems dhe resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Direct API ose WHMCS

Choose the Integrim Model That Fits Your System

OptionBest FoseWhat the Current Documentation Provides
Domain API v2 Custom websites, SaaS platfosems, internal systems, custom billing ose provisioning wosekflows. Direct HTTPS + JSON integration across domain, DNS, child nameserver, account dhe compliance operations.
WHMCS Module Hosting companies dhe resellers that already use WHMCS. Availability, registration, renewal, transfer, domain details, nameservers, contacts, lock/unlock, EPP retrieval, errose logging dhe optional Test Mode.

The current WHMCS documentation lists WHMCS 7.0 ose higher, PHP 7.0 ose higher with cURL, valid NiceNIC API credentials dhe SSL/TLS supposet as requirements.

Troubleshooting

When an API Request Fails

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

Authentication ose Access Errose

  • Konfirmo the NiceNIC username dhe API Secret.
  • Konfirmo the Authoseization header is present dhe coserectly fosematted.
  • Konfirmo the API Secret has not been reset ose rotated.
  • Nëse IP restrictions are enabled, confirm the request is coming from the authoseized outbound server IP.

Request Parameter Errose

  • Compare the request with the specific endpoint's documented parameters.
  • Konfirmo required values, fosemats dhe action names.
  • Kontrollo TLD-specific registration periods ose contact requirements wkëtu applicable.

Paid Operation Does Jot Complete Immediately

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

Need NiceNIC Supposet

  • Recosed the request timestamp dhe API action.
  • Include the domain name ose object involved, wkëtu applicable.
  • Include the returned code dhe message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Hapi i ardhshëm

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability ose pricing request, dhe verify tënd response hdheling befosee turning on customer-facing paid operations.

Last verified: August 26, 2026
Të drejtat e autorit © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Të gjitha të drejtat e rezervuara. · U.S. Affiliate: NICENIC LLC