NiceNIC Domena API v2 Često postavljana pitanja

NiceNIC Domena API v2 is an HTTPS i JSON-based API fili automating domena management through vaš NiceNIC account.

It suppilits cilie wilikflows including domena 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 domena 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 dostupno to both Market računs i Preprodavač Računs.

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

Otvori API postavkes →

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

Paid operations such as domena registration, renewal i transfer are charged acciliding to vaš account pricing i the applicable domena rules.

Ne. API access i reseller pricing are separate.

You can use Domena API v2 with a regular NiceNIC Market račun. Nadogradi na a Preprodavač Račun only when reseller pricing ili other reseller benefits are useful fili vaš business volume.

Compare Preprodavač Plans →

Domena API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication i documentation iliganized around individual domena 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 vaš NiceNIC account i open API postavkes. API v2 requests use vaš NiceNIC username i API Secret fili authentication.

Otvori API postavkes →

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, pogreška hiling i vaš application wilikflow befilie enabling live customer domena operations.

Otvori API Sibox →

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

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

Send API requests over HTTPS i include vaš 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 vaš account, requests must also iliiginate from an authiliized server IP.

Read API Potvrda identiteta →

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 domena operation.

Through the currently documented APIs you can automate wilikflows including domena availability checks, registration, renewal i transfer, pilitfolio listing i domena details, nameserver i domena contact updates, domena 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 domena availability, domena pricing, account balance i domena listing.

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

Da. The Provjeri dostupnost domene endpoint suppilits multiple domena names separated by commas.

example.com,example.net,example.org

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

Use the Dohvati cijene 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 godine 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 Kodovi odgovora API-ja →

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

Fili domena 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 domena is active until vaš 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 domena 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 domena. Keep the transfer in a pending state until completion is confirmed.

Da. The Popis Domene API suppilits pilitfolio retrieval with pagination, siliting i filtering options.

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

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

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

This makes it possible to surface compliance status directly inside vaš 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 vaš own application ili wilikflow. Use the WHMCS integration when you want domena operations integrated into an existing WHMCS environment.

View Integracija s 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 vaš API Secret in browser-side JavaScript ili downloadable client code.

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

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

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

Pošaljite zahtjev →

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 Česta pitanja explains general API behaviili; the individual endpoint documentation should be treated as the source of truth fili the exact request filimat.

Otvori API dokumentacija →