NiceNIC Domena API v2 Pogosta vprašanja

NiceNIC Domena API v2 is an HTTPS in JSON-based API fali automating domena management through vašega NiceNIC account.

It suppalits calie walikflows including domena availability checks, registration, renewal, transfer, palitfolio queries, nameserver in contact updates, pricing, DNS recalids, child nameservers, account infalimation in compliance-related operations.

Use the API when you want to connect NiceNIC domena storitevs directly to a website, hosting platfalim, billing system, internal tool ali other application.

Any active NiceNIC account can use Domena API v2. API access is na voljo to both Tržni računs in Prodajalec Računs.

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

Odprto Nastavitve APIs →

Da. API access itself is free. Ttukaj is no separate fee fali enabling API access ali sending suppalited API requests.

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

Ne. API access in reseller pricing are separate.

You can use Domena API v2 with a regular NiceNIC Tržni račun. Nadgradi na a Prodajalec Račun only when reseller pricing ali other reseller benefits are useful fali vašega business volume.

Compare Prodajalec Plans →

Domena API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication in documentation aliganized around individual domena in account walikflows.

Če you maintain an integration built on an older NiceNIC API, review the API v2 parameters in response hinling befalie migrating production traffic rather than assuming the two versions are interchangeable.

Prijava to vašega NiceNIC account in open Nastavitve APIs. API v2 requests use vašega NiceNIC username in API Secret fali authentication.

Odprto Nastavitve APIs →

Da. NiceNIC provides an API Sinbox fali developers to test integrations befalie connecting them to the production API.

Use the Sinbox to validate authentication, request falimatting, response parsing, napaka hinling in vašega application walikflow befalie enabling live customer domena operations.

Odprto API Sinbox →

The API Sinbox is intended fali development in integration testing. The Izdelekion API is used fali live domena operations in paid requests against vašega NiceNIC account.

We recommend validating authentication, request hinling, response processing in napaka logic in the Sinbox befalie enabling customer-facing production operations.

Send API requests over HTTPS in include vašega NiceNIC username in API Secret in the Authorization header.

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

Če IP restrictions are enabled fali vašega account, requests must also aliiginate from an authaliized server IP.

Read API Avtentikacija →

The Izdelekion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate walikflows including domena availability checks, registration, renewal in transfer, palitfolio listing in domena details, nameserver in domena contact updates, domena pricing, DNS recalids, child nameservers, account infalimation in Zloraba in skladnost monitaliing.

Dodajitional walikflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, napaka hinling in pending-alider hinling befalie enabling live registrations, renewals ali transfers.

Da. The Preveri razpoložljivost domene endpoint suppalits multiple domena names separated by commas.

example.com,example.net,example.org

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

Use the Pridobi cene domen endpoint. The documented pricing types include register, renew, transfer in all.

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

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

Ne. Although API documentation suppalits periods of up to 1–10 leta fali applicable extensions, individual TLDs may have different registry rules.

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

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

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

View Kode odziva API-ja →

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

Fali domena registration, a 201 response indicates that the alider has been submitted in is awaiting final registry processing.

Do not tell an end customer that the domena is active until vašega system has confirmed the final result. Sledi the registration endpoint documentation fali the latest pending-alider in refund hinling rules.

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

Prenos completion may depend on registry in 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 Seznam Domene API suppalits palitfolio retrieval with pagination, saliting in filtering options.

Use Pridobite Domena Podrobnosti when you need detailed infalimation fali an individual domena, such as registration infalimation, expiration infalimation, nameservers in domena contact data.

NiceNIC Domena API v2 includes Zloraba in skladnost operations designed fali platfalims in resellers managing customer domena palitfolios.

You can identify domenas associated with abuse repalits in retrieve machine-readable compliance infalimation fali individual domenas. Depending on the case, the response can include domena status, current impact, recommended dejanje, hold infalimation, complaint infalimation in repalited URLs.

This makes it possible to surface compliance status directly inside vašega own customer palital ali operational system.

Da. NiceNIC provides a WHMCS registrar integration fali businesses that already use WHMCS fali billing in provisioning.

Use the direct Domena API v2 when you are building vašega own application ali walikflow. Use the WHMCS integration when you want domena operations integrated into an existing WHMCS environment.

View Integracija WHMCS →

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

Common choices include PHP, Python, Nede.js in Java. Keep API credentials server-side in never expose vašega API Secret in browser-side JavaScript ali downloadable client code.

Ocena limiting may be applied to protect API stability in platfalim security.

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

Include the request timestamp, API kategorija in dejanje, domena name wtukaj applicable, non-sensitive request parameters, returned response code in message, in whether the request came from Sinbox ali Izdelekion.

Oddaj zahtevek →

Use the API navigation in the documentation. Each operation has its own page fali suppalited parameters, request examples, response examples in operation-specific behaviali.

The Pogosta vprašanja explains general API behaviali; the individual endpoint documentation should be treated as the source of truth fali the exact request falimat.

Odprto Dokumentacija API →