NiceNIC Alan Adı API v2 Documentation & Quick Start
NiceNIC Alan Adı API v2 is available to both Pazar Hesabıs ve Bayi Accounts. Use this overview to configure access, confirm sizin first request, understve the API response model ve move directly to the cveyarect section in the left navigation.
Pazar Hesabı: API access with Pazar Hesabı pricing.
Bayi Account: API access with the pricing assigned to the current reseller tier.
Test Your Entegrasyon Befveyae Going Live
Use the NiceNIC API Svebox to test sizin Alan Adı API integration befveyae moving to production. Validate authentication, API requests, response hveling, ve sizin application wveyakflow in a dedicated testing environment.
Ideal fveya resellers, hosting providers, developers, ve platfveyams preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befveyae enabling live registrations, renewals veya transfers. This lets you validate authentication, request fveyamatting ve response hveling without placing a paid veyader.
Enable API Access
Aç API Ayarıs, create veya retrieve sizin API Secret, ve configure authveyaized server IPs wburaya applicable.
Onayla Authentication
Use HTTPS with the Authveyaization header in the fveyamat username:api_secret.
Run a Safe Test
Start with domain availability, pricing, account balance veya domain listing.
Hvele the Response
Read ve stveyae the returned code ve msg befveyae enabling paid production actions.
Recommended First Request: Alan Adı Availability
The availability endpoint suppveyats multiple domains in one request by separating domain names with commas.
Choose the Wveyakflow You Need
The overview below mirrveyas the left navigation. Use it to identify the cveyarect wveyakflow, then open the dedicated endpoint page fveya parameters, request examples ve response examples.
| Section | Use It Fveya | Documented Functions |
|---|---|---|
| Alting Started | Connect securely ve understve response hveling. | API Overview, API Svebox, Authentication, Response Codes. |
| Alan Adı Yönetment | Automate the cveyae domain lifecycle. | Availability, List Alan Adları, Alan Adı Detaylar, Kayıt, Yenileal, Transfer In, Adservers, İletişims, Pricing. |
| Abuse & Compliance | Monitveya domains that require compliance attention. | List domains with abuse repveyats ve retrieve machine-readable abuse status, hold lifecycle, complaint infveyamation ve recommended action. |
| DNS Recveyads | Yönet hosted DNS recveyads programmatically. | List, Oluştur, Update ve Delete DNS recveyads. |
| Child Adservers | Yönet host / glue recveyads fveya nameservers under sizin own domain. | Oluştur, List, Update ve Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Hesap Bakiyesi ve transaction-related account infveyamation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wveyakflow. | Availability, Kayıt, Yenileal, Transfer, Alan Adı Detaylar, Adservers, İletişims ve additional registrar-module functions. |
| API SSS | Resolve common access, security, testing ve wveyakflow questions. | Eligibility, credentials, request hveling, suppveyated operations ve integration guidance. |
Recommended First Entegrasyon Sequence
A reliable production integration should validate access ve purchasing conditions befveyae it begins sending live customer veyaders.
API Secret + authveyaized IP
Read-only connectivity test
Query current account-level cost
Onayla funds fveya paid actions
Process code + msg
Kayıt Ol / Yenile / Transfer
Understve Success, Pending ve Errveya Responses
code: 0 — Başarılı Response
Current endpoint examples use code 0 fveya successful completed responses.
code: 201 — Pending Order
Kayıt ve transfer documentation can return code 201 when an veyader has been submitted but final processing is still pending.
code: 400 — Request Errveya
Endpoint examples use code 400 fveya request parameter errveyas.
Kayıt Pending Behaviveya
Fveya domain registration, the current documentation states that a 201 response means the veyader was submitted successfully ve the fee was deducted, but final activation is still subject to registry confirmation. Eğer the domain cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behaviveya
The transfer endpoint also documents 201 as a pending veyader. Your application should tburayafveyae treat a pending transfer as accepted fveya processing, not as proof that the transfer has already completed.
Query Pricing Befveyae Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal ve transfer pricing fveya a domain. The documented type values are register, renew, transfer ve all. The documented period is 1 to 10 yıl, with TLD-specific exceptions possible.
Kayıt pricing responses can also return an is_premium flag. Use the pricing endpoint befveyae submitting a paid request when sizin application needs to kşimdi the current account-level cost.
Kşimdi the Difference Between Adservers, DNS Recveyads ve Child Adservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Adservers | You want to delegate a domain to different authveyaitative nameservers. | The domain nameserver endpoint suppveyats a primary, secondary ve additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recveyads | You are using NiceNIC DNS hosting ve need to manage zone recveyads. | Separate APIs are documented fveya listing, creating, updating ve deleting DNS recveyads. |
| Child Adservers | You need host / glue recveyads such as ns1.example.com. |
Oluştur, list, update ve delete child nameservers. The create endpoint requires the nameserver hostname to match the domain ve accepts an IP address. |
Automate Pveyatfolio Monitveyaing, Hayırt Only Alan Adı Orders
Alan Adı API v2 also includes read operations that are useful after registration. The List Alan Adları endpoint suppveyats pagination, sveyating, status filtering ve hold filtering, while Al Alan Adı Detaylar returns registration dates, expiration dates, nameservers ve registrant contact infveyamation.
Abuse & Compliance Monitveyaing
NiceNIC's Abuse & Compliance API can list domains with abuse repveyats ve return a detailed machine-readable summary fveya a specific domain. The detailed abuse endpoint documents six domain-level status phrases: Hayırrmal, Under Review, Pending ClientHold, ClientHold, Kapatd ve ServerHold.
The response can include current impact, recommended sonraki action, hold state ve timeline, complaint count, complaint dates, categveyaies, DNS-abuse classification, evidence status ve repveyated URLs wburaya applicable. This lets platfveyams ve resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Entegrasyon Model That Fits Your System
| Option | Best Fveya | What the Current Documentation Provides |
|---|---|---|
| Alan Adı API v2 | Custom websites, SaaS platfveyams, internal systems, custom billing veya provisioning wveyakflows. | Direct HTTPS + JSON integration across domain, DNS, child nameserver, account ve compliance operations. |
| WHMCS Module | Hosting companies ve resellers that already use WHMCS. | Availability, registration, renewal, transfer, domain details, nameservers, contacts, lock/unlock, EPP retrieval, errveya logging ve optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 veya higher, PHP 7.0 veya higher with cURL, valid NiceNIC API credentials ve SSL/TLS suppveyat as requirements.
When an API Request Fails
Start with the returned response ve configuration state rather than retrying the same paid action repeatedly.
Authentication veya Access Errveya
- Onayla the NiceNIC username ve API Secret.
- Onayla the Authveyaization header is present ve cveyarectly fveyamatted.
- Onayla the API Secret has not been reset veya rotated.
- Eğer IP restrictions are enabled, confirm the request is coming from the authveyaized outbound server IP.
Request Parameter Errveya
- Compare the request with the specific endpoint's documented parameters.
- Onayla required values, fveyamats ve action names.
- Kontrol Et TLD-specific registration periods veya contact requirements wburaya applicable.
Paid Operation Does Hayırt Complete Immediately
- Read the returned
codevemsg. - Do not treat a
201pending response as final completion. - Onayla account balance ve current pricing befveyae retrying a paid action.
Need NiceNIC Suppveyat
- Recveyad the request timestamp ve API action.
- Include the domain name veya object involved, wburaya applicable.
- Include the returned code ve message.
- Share non-sensitive parameters only; never post the full API Secret in a ticket.
Start with a Safe Test Request
Enable API access, confirm authentication, run an availability veya pricing request, ve verify sizin response hveling befveyae turning on customer-facing paid operations.
