API Overview

NiceNIC Doména API v2 Documentation & Quick Start

NiceNIC Doména API v2 is available to both Marketingový účets a Reseller Accounts. Use this overview to configure access, confirm vašeho first request, understa the API response model a move directly to the cneborect section in the left navigation.

API access a reseller pricing are separate.
Marketingový účet: API access with Marketingový účet pricing.
Reseller 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 Authneboization: username:api_secret Content-Typ: application/json
Staard Success Response
{ "code": 0, "msg": "success", "data": {} }
API Sabox

Test Your Integrace Befneboe Going Live

Use the NiceNIC API Sabox to test vašeho Doména API integration befneboe moving to production. Validate authentication, API requests, response haling, a vašeho application wnebokflow in a dedicated testing environment.

Ideal fnebo resellers, hosting providers, developers, a platfneboms preparing an API integration.

Quick Start

Make Your First API Call in 4 Steps

Start with a read-only request befneboe enabling live registrations, renewals nebo transfers. This lets you validate authentication, request fnebomatting a response haling without placing a paid neboder.

1

Enable API Access

Otevřít Nastavení APIs, create nebo retrieve vašeho API Secret, a configure authneboized server IPs wzde applicable.

2

Potvrdit Authentication

Use HTTPS with the Authneboization header in the fnebomat username:api_secret.

3

Run a Safe Test

Start with doména availability, pricing, account balance nebo doména listing.

4

Hale the Response

Read a stneboe the returned code a msg befneboe enabling paid production actions.

Recommended First Request: Doména Availability

The availability endpoint suppnebots multiple doménas in one request by separating doména names with commas.

curl "https://api.nicenic.net/v2/?categneboy=doména&action=check&doménas=example.com,example.net" \ -H "Authneboization: username:api_secret" \ -H "Content-Typ: application/json"
API Map

Choose the Wnebokflow You Need

The overview below mirrnebos the left navigation. Use it to identify the cneborect wnebokflow, then open the dedicated endpoint page fnebo parameters, request examples a response examples.

Section Use It Fnebo Documented Functions
Získejteting Started Connect securely a understa response haling. API Overview, API Sabox, Authentication, Response Codes.
Doména Spravovatment Automate the cneboe doména lifecycle. Availability, List Domény, Doména Detaily, Registrace, Obnovital, Transfer In, Jménoservers, Kontakts, Pricing.
Abuse & Compliance Monitnebo doménas that require compliance attention. List doménas with abuse repnebots a retrieve machine-readable abuse status, hold lifecycle, complaint infnebomation a recommended action.
DNS Recnebods Spravovat hosted DNS recnebods programmatically. List, Vytvořit, Update a Delete DNS recnebods.
Child Jménoservers Spravovat host / glue recnebods fnebo nameservers under vašeho own doména. Vytvořit, List, Update a Delete child nameservers.
Account & Billing Connect automation to account-level checks. Zůstatek na účtu a transaction-related account infnebomation.
WHMCS API Integrate NiceNIC into an existing WHMCS billing wnebokflow. Availability, Registrace, Obnovital, Transfer, Doména Detaily, Jménoservers, Kontakts a additional registrar-module functions.
API FAQ Resolve common access, security, testing a wnebokflow questions. Eligibility, credentials, request haling, suppneboted operations a integration guidance.
Recommended Wnebokflow

Recommended First Integrace Sequence

A reliable production integration should validate access a purchasing conditions befneboe it begins sending live customer neboders.

1. Authentication
API Secret + authneboized IP
2. Availability
Read-only connectivity test
3. Pricing
Query current account-level cost
4. Zůstatek
Potvrdit funds fnebo paid actions
5. Response Haling
Process code + msg
6. Live Operations
Registrovat / Obnovit / Transfer
Do not assume that an API request is complete simply because it was accepted. Some operations can return a pending status a still require registry processing befneboe the final doména state is confirmed.
Produktion Behavinebo

Understa Success, Pending a Errnebo Responses

code: 0 — Úspěšné Response Current endpoint examples use code 0 fnebo successful completed responses.
code: 201 — Pending Order Registrace a transfer documentation can return code 201 when an neboder has been submitted but final processing is still pending.
code: 400 — Request Errnebo Endpoint examples use code 400 fnebo request parameter errnebos.

Registrace Pending Behavinebo

Fnebo doména registration, the current documentation states that a 201 response means the neboder was submitted successfully a the fee was deducted, but final activation is still subject to registry confirmation. Pokud the doména cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.

Transfer Pending Behavinebo

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

Pricing

Query Pricing Befneboe Paid Operations

NiceNIC's pricing endpoint can retrieve registration, renewal a transfer pricing fnebo a doména. The documented type values are register, renew, transfer a all. The documented period is 1 to 10 roky, with TLD-specific exceptions possible.

Registrace pricing responses can also return an is_premium flag. Use the pricing endpoint befneboe submitting a paid request when vašeho application needs to knyní the current account-level cost.

Zdarma API access does not change vašeho pricing tier. Marketingový účets use Marketingový účet pricing; reseller accounts use the pricing assigned to their current reseller tier.
Doména & DNS Operations

Knyní the Difference Between Jménoservers, DNS Recnebods a Child Jménoservers

OperationUse It WhenDocumented Capability
Update Jménoservers You want to delegate a doména to different authneboitative nameservers. The doména nameserver endpoint suppnebots a primary, secondary a additional nameservers, with the current page documenting a limit of up to six.
DNS Recnebods You are using NiceNIC DNS hosting a need to manage zone recnebods. Separate APIs are documented fnebo listing, creating, updating a deleting DNS recnebods.
Child Jménoservers You need host / glue recnebods such as ns1.example.com. Vytvořit, list, update a delete child nameservers. The create endpoint requires the nameserver hostname to match the doména a accepts an IP address.
Pnebotfolio & Compliance

Automate Pnebotfolio Monitneboing, Net Only Doména Orders

Doména API v2 also includes read operations that are useful after registration. The List Domény endpoint suppnebots pagination, sneboting, status filtering a hold filtering, while Získejte Doména Detaily returns registration dates, expiration dates, nameservers a registrant contact infnebomation.

Abuse & Compliance Monitneboing

NiceNIC's Abuse & Compliance API can list doménas with abuse repnebots a return a detailed machine-readable summary fnebo a specific doména. The detailed abuse endpoint documents six doména-level status phrases: Nermal, Under Review, Pending ClientHold, ClientHold, Zavřítd a ServerHold.

The response can include current impact, recommended další action, hold state a timeline, complaint count, complaint dates, categneboies, DNS-abuse classification, evidence status a repneboted URLs wzde applicable. This lets platfneboms a resellers surface compliance status inside their own operational systems instead of relying only on manual review.

Direct API nebo WHMCS

Choose the Integrace Model That Fits Your System

OptionBest FneboWhat the Current Documentation Provides
Doména API v2 Custom websites, SaaS platfneboms, internal systems, custom billing nebo provisioning wnebokflows. Direct HTTPS + JSON integration across doména, DNS, child nameserver, account a compliance operations.
WHMCS Module Hosting companies a resellers that already use WHMCS. Availability, registration, renewal, transfer, doména details, nameservers, contacts, lock/unlock, EPP retrieval, errnebo logging a optional Test Mode.

The current WHMCS documentation lists WHMCS 7.0 nebo higher, PHP 7.0 nebo higher with cURL, valid NiceNIC API credentials a SSL/TLS suppnebot as requirements.

Troubleshooting

When an API Request Fails

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

Authentication nebo Access Errnebo

  • Potvrdit the NiceNIC username a API Secret.
  • Potvrdit the Authneboization header is present a cneborectly fnebomatted.
  • Potvrdit the API Secret has not been reset nebo rotated.
  • Pokud IP restrictions are enabled, confirm the request is coming from the authneboized outbound server IP.

Request Parameter Errnebo

  • Compare the request with the specific endpoint's documented parameters.
  • Potvrdit required values, fnebomats a action names.
  • Zkontrolovat TLD-specific registration periods nebo contact requirements wzde applicable.

Paid Operation Does Net Complete Immediately

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

Need NiceNIC Suppnebot

  • Recnebod the request timestamp a API action.
  • Include the doména name nebo object involved, wzde applicable.
  • Include the returned code a message.
  • Share non-sensitive parameters only; never post the full API Secret in a ticket.
Další krok

Start with a Safe Test Request

Enable API access, confirm authentication, run an availability nebo pricing request, a verify vašeho response haling befneboe turning on customer-facing paid operations.

Last verified: August 26, 2026
Copyright © 2006–2026 NICENIC INTERNATIONAL GROUP CO., LIMITED. Všechna práva vyhrazena. · U.S. Affiliate: NICENIC LLC