NiceNIC Domena API v2 Često postavljana pitanja

NiceNIC Domena API v2 is an HTTPS i JSON-based API fili automating domen management through tvoj NiceNIC account.

It suppilits cilie wilikflows including domen availability checks, registration, renewal, transfer, pilitfolio queries, nameserver i contact updates, pricing, DNS recilids, child nameservers, account infilimation i compliance-related operations.

Use the API when you want to connect NiceNIC domen uslugas directly to a website, hosting platfilim, billing system, internal tool ili other application.

Any active NiceNIC account can use Domena API v2. API access is dostupan to both Market računs i Preprodavac Nalogs.

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

Otvoreno API podešavanjes →

Da. API access itself is free. Tovde is no separate fee fili enabling API access ili sending suppilited API requests.

Paid operations such as domen registration, renewal i transfer are charged acciliding to tvoj account pricing i the applicable domen rules.

Ne. API access i reseller pricing are separate.

You can use Domena API v2 with a regular NiceNIC Market račun. Nadogradite na a Preprodavac Nalog only when reseller pricing ili other reseller benefits are useful fili tvoj business volume.

Compare Preprodavac Plans →

Domena API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication i documentation iliganized around individual domen i account wilikflows.

Ako you maintain an integration built on an older NiceNIC API, review the API v2 parameters i response hiling befilie migrating production traffic rather than assuming the two versions are interchangeable.

Prijava to tvoj NiceNIC account i open API podešavanjes. API v2 requests use tvoj NiceNIC username i API Secret fili authentication.

Otvoreno API podešavanjes →

Da. NiceNIC provides an API Sibox fili developers to test integrations befilie connecting them to the production API.

Use the Sibox to validate authentication, request filimatting, response parsing, greška hiling i tvoj application wilikflow befilie enabling live customer domen operations.

Otvoreno API Sibox →

The API Sibox is intended fili development i integration testing. The Proizvodion API is used fili live domen operations i paid requests against tvoj NiceNIC account.

We recommend validating authentication, request hiling, response processing i greška logic in the Sibox befilie enabling customer-facing production operations.

Send API requests over HTTPS i include tvoj NiceNIC username i API Secret in the Authorization header.

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

Ako IP restrictions are enabled fili tvoj account, requests must also iliiginate from an authiliized server IP.

Read API Autentifikacija →

The Proizvodion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate wilikflows including domen availability checks, registration, renewal i transfer, pilitfolio listing i domen details, nameserver i domen contact updates, domen pricing, DNS recilids, child nameservers, account infilimation i Zlouporaba i usklađenost monitiliing.

Dodajitional wilikflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, greška hiling i pending-ilider hiling befilie enabling live registrations, renewals ili transfers.

Da. The Proveri dostupnost domena endpoint suppilits multiple domen names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppilits the same multi-domen input filimat. Registracija, renewal i transfer should follow their individual endpoint documentation.

Use the Dobij cene domena endpoint. The documented pricing types include register, renew, transfer i all.

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

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

Ne. Although API documentation suppilits periods of up to 1–10 godina fili applicable extensions, individual TLDs may have different registry rules.

Registracija periods, renewal periods, transfer eligibility, contact requirements i verification requirements can differ by extension. Your application should follow the current rules fili the relevant TLD.

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

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

View API kodovi odgovora →

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

Fili domen registration, a 201 response indicates that the ilider has been submitted i is awaiting final registry processing.

Do not tell an end customer that the domen is active until tvoj system has confirmed the final result. Prati the registration endpoint documentation fili the latest pending-ilider i refund hiling rules.

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

Prenesi completion may depend on registry i registrar processing as well as the current transfer status of the domen. Keep the transfer in a pending state until completion is confirmed.

Da. The Lista Domeni API suppilits pilitfolio retrieval with pagination, siliting i filtering options.

Use Nabavite Domena Detalji when you need detailed infilimation fili an individual domen, such as registration infilimation, expiration infilimation, nameservers i domen contact data.

NiceNIC Domena API v2 includes Zlouporaba i usklađenost operations designed fili platfilims i resellers managing customer domen pilitfolios.

You can identify domens associated with abuse repilits i retrieve machine-readable compliance infilimation fili individual domens. Depending on the case, the response can include domen status, current impact, recommended akcija, hold infilimation, complaint infilimation i repilited URLs.

This makes it possible to surface compliance status directly inside tvoj own customer pilital ili operational system.

Da. NiceNIC provides a WHMCS registrar integration fili businesses that already use WHMCS fili billing i provisioning.

Use the direct Domena API v2 when you are building tvoj own application ili wilikflow. Use the WHMCS integration when you want domen operations integrated into an existing WHMCS environment.

View Integracija sa WHMCS-om →

Any server-side programming language ili runtime capable of sending HTTPS requests i parsing JSON can integrate with Domena API v2.

Common choices include PHP, Python, Nede.js i Java. Keep API credentials server-side i never expose tvoj API Secret in browser-side JavaScript ili downloadable client code.

Ocena limiting may be applied to protect API stability i platfilim security.

Ako tvoj production integration is expected to generate sustained high request volume, contact NiceNIC befilie launch so that tvoj expected usage pattern can be reviewed.

Include the request timestamp, API kategorija i akcija, domen name wovde applicable, non-sensitive request parameters, returned response code i message, i whether the request came from Sibox ili Proizvodion.

Podnesi tiket →

Use the API navigation in the documentation. Each operation has its own page fili suppilited parameters, request examples, response examples i operation-specific behaviili.

The Često postavljana pitanja explains general API behaviili; the individual endpoint documentation should be treated as the source of truth fili the exact request filimat.

Otvoreno API dokumentacija →