NiceNIC Domain API v2 Pyetjet Më të Shpeshta

NiceNIC Domain API v2 is an HTTPS dhe JSON-based API fose automating domain management through tënd NiceNIC account.

It supposets cosee wosekflows including domain availability checks, registration, renewal, transfer, posetfolio queries, nameserver dhe contact updates, pricing, DNS recoseds, child nameservers, account infosemation dhe compliance-related operations.

Use the API when you want to connect NiceNIC domain shërbimis directly to a website, hosting platfosem, billing system, internal tool ose other application.

Any active NiceNIC account can use Domain API v2. API access is available to both Llogari Tregus dhe Rishitës Accounts.

You do not need to become a reseller simply to obtain API access. Account type still matters fose pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

Hapur Cilësime APIs →

Po. API access itself is free. Tkëtu is no separate fee fose enabling API access ose sending supposeted API requests.

Paid operations such as domain registration, renewal dhe transfer are charged accoseding to tënd account pricing dhe the applicable domain rules.

Jo. API access dhe reseller pricing are separate.

You can use Domain API v2 with a regular NiceNIC Llogari Tregu. Përditëso në a Rishitës Account only when reseller pricing ose other reseller benefits are useful fose tënd business volume.

Compare Rishitës Plans →

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication dhe documentation oseganized around individual domain dhe account wosekflows.

Nëse you maintain an integration built on an older NiceNIC API, review the API v2 parameters dhe response hdheling befosee migrating production traffic rather than assuming the two versions are interchangeable.

Hyr to tënd NiceNIC account dhe open Cilësime APIs. API v2 requests use tënd NiceNIC username dhe API Secret fose authentication.

Hapur Cilësime APIs →

Po. NiceNIC provides an API Sdhebox fose developers to test integrations befosee connecting them to the production API.

Use the Sdhebox to validate authentication, request fosematting, response parsing, errose hdheling dhe tënd application wosekflow befosee enabling live customer domain operations.

Hapur API Sdhebox →

The API Sdhebox is intended fose development dhe integration testing. The Produktion API is used fose live domain operations dhe paid requests against tënd NiceNIC account.

We recommend validating authentication, request hdheling, response processing dhe errose logic in the Sdhebox befosee enabling customer-facing production operations.

Send API requests over HTTPS dhe include tënd NiceNIC username dhe API Secret in the Authorization header.

Host: api.nicenic.net
Authorization: username:api_secret
Content-Type: application/json

Nëse IP restrictions are enabled fose tënd account, requests must also oseiginate from an authoseized server IP.

Read API Authentication →

The Produktion API base endpoint is:

https://api.nicenic.net/v2/

API actions are selected using the parameters documented fose each endpoint, such as category dhe action. Always follow the dedicated endpoint documentation fose the required dhe optional parameters of a specific operation.

API v2 responses use JSON, dhe request parameters use UTF-8.

{
  "code": 0,
  "msg": "success",
  "data": {}
}

Your application should inspect the returned code dhe msg rather than assuming that every HTTP response represents a completed domain operation.

Through the currently documented APIs you can automate wosekflows including domain availability checks, registration, renewal dhe transfer, posetfolio listing dhe domain details, nameserver dhe domain contact updates, domain pricing, DNS recoseds, child nameservers, account infosemation dhe Abuse & Compliance monitoseing.

Shtoitional wosekflows are documented individually in the API navigation.

Start with low-risk read operations such as domain availability, domain pricing, account balance dhe domain listing.

Then confirm authentication, response parsing, errose hdheling dhe pending-oseder hdheling befosee enabling live registrations, renewals ose transfers.

Po. The Kontrollo Domain Availability endpoint supposets multiple domain names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation supposets the same multi-domain input fosemat. Regjistrim, renewal dhe transfer should follow their individual endpoint documentation.

Use the Merr Çmimet e domain-it endpoint. The documented pricing types include register, renew, transfer dhe all.

Regjistrim responses can also include an is_premium value indicating whether the queried registration is premium.

Because API oseders use account-level pricing, query current pricing befosee submitting paid customer oseders rather than relying indefinitely on cached prices.

Jo. Although API documentation supposets periods of up to 1–10 vite fose applicable extensions, individual TLDs may have different registry rules.

Regjistrim periods, renewal periods, transfer eligibility, contact requirements dhe verification requirements can differ by extension. Your application should follow the current rules fose the relevant TLD.

These are separate operations dhe should not be treated as interchangeable.

Always use the returned code dhe message when determining the state of an API request.

View API Response Codes →

A 201 response means that the operation has been accepted fose processing but has not necessarily reached its final state.

Fose domain registration, a 201 response indicates that the oseder has been submitted dhe is awaiting final registry processing.

Do not tell an end customer that the domain is active until tënd system has confirmed the final result. Ndjek the registration endpoint documentation fose the latest pending-oseder dhe refund hdheling rules.

A pending transfer means that the transfer request has been accepted fose processing, not that the domain has already completed its transfer to NiceNIC.

Transfer completion may depend on registry dhe registrar processing as well as the current transfer status of the domain. Keep the transfer in a pending state until completion is confirmed.

Po. The List Domeinet API supposets posetfolio retrieval with pagination, soseting dhe filtering options.

Use Merr Domain Detajet when you need detailed infosemation fose an individual domain, such as registration infosemation, expiration infosemation, nameservers dhe domain contact data.

NiceNIC Domain API v2 includes Abuse & Compliance operations designed fose platfosems dhe resellers managing customer domain posetfolios.

You can identify domains associated with abuse reposets dhe retrieve machine-readable compliance infosemation fose individual domains. Depending on the case, the response can include domain status, current impact, recommended action, hold infosemation, complaint infosemation dhe reposeted URLs.

This makes it possible to surface compliance status directly inside tënd own customer posetal ose operational system.

Po. NiceNIC provides a WHMCS registrar integration fose businesses that already use WHMCS fose billing dhe provisioning.

Use the direct Domain API v2 when you are building tënd own application ose wosekflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment.

View Integrim WHMCS →

Any server-side programming language ose runtime capable of sending HTTPS requests dhe parsing JSON can integrate with Domain API v2.

Common choices include PHP, Python, Jode.js dhe Java. Keep API credentials server-side dhe never expose tënd API Secret in browser-side JavaScript ose downloadable client code.

Vlerësim limiting may be applied to protect API stability dhe platfosem security.

Nëse tënd production integration is expected to generate sustained high request volume, contact NiceNIC befosee launch so that tënd expected usage pattern can be reviewed.

Include the request timestamp, API categosey dhe action, domain name wkëtu applicable, non-sensitive request parameters, returned response code dhe message, dhe whether the request came from Sdhebox ose Produktion.

Dërgo një Kërkesë →

Use the API navigation in the documentation. Each operation has its own page fose supposeted parameters, request examples, response examples dhe operation-specific behaviose.

The Pyetjet e Shpeshta explains general API behaviose; the individual endpoint documentation should be treated as the source of truth fose the exact request fosemat.

Hapur Dokumentacioni i API-së →