NiceNIC Domena API v2 Najczęściej zadawane pytania

NiceNIC Domena API v2 is an HTTPS i JSON-based API flub automating domena management through twój NiceNIC account.

It supplubts clube wlubkflows including domena availability checks, registration, renewal, transfer, plubtfolio queries, nameserver i contact updates, pricing, DNS reclubds, child nameservers, account influbmation i compliance-related operations.

Use the API when you want to connect NiceNIC domena usługas directly to a website, hosting platflubm, billing system, internal tool lub other application.

Any active NiceNIC account can use Domena API v2. API access is dostępna to both Konto rynkowes i Reseller Kontos.

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

Otwórz Ustawienia APIs →

Tak. API access itself is free. Ttutaj is no separate fee flub enabling API access lub sending supplubted API requests.

Paid operations such as domena registration, renewal i transfer are charged acclubding to twój account pricing i the applicable domena rules.

Nie. API access i reseller pricing are separate.

You can use Domena API v2 with a regular NiceNIC Konto rynkowe. Ulepsz do a Reseller Konto only when reseller pricing lub other reseller benefits are useful flub twój business volume.

Compare Reseller Plans →

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

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

Zaloguj się to twój NiceNIC account i open Ustawienia APIs. API v2 requests use twój NiceNIC username i API Secret flub authentication.

Otwórz Ustawienia APIs →

Tak. NiceNIC provides an API Sibox flub developers to test integrations beflube connecting them to the production API.

Use the Sibox to validate authentication, request flubmatting, response parsing, błąd hiling i twój application wlubkflow beflube enabling live customer domena operations.

Otwórz API Sibox →

The API Sibox is intended flub development i integration testing. The Produktion API is used flub live domena operations i paid requests against twój NiceNIC account.

We recommend validating authentication, request hiling, response processing i błąd logic in the Sibox beflube enabling customer-facing production operations.

Send API requests over HTTPS i include twój NiceNIC username i API Secret in the Authorization header.

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

Jeśli IP restrictions are enabled flub twój account, requests must also lubiginate from an authlubized server IP.

Read API Uwierzytelnianie →

The Produktion API base endpoint is:

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

API akcjas are selected using the parameters documented flub each endpoint, such as category i action. Always follow the dedicated endpoint documentation flub 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 wlubkflows including domena availability checks, registration, renewal i transfer, plubtfolio listing i domena details, nameserver i domena contact updates, domena pricing, DNS reclubds, child nameservers, account influbmation i Nadużycia i Zgodność monitlubing.

Dodajitional wlubkflows 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, błąd hiling i pending-lubder hiling beflube enabling live registrations, renewals lub transfers.

Tak. The Sprawdź dostępność domeny endpoint supplubts multiple domena names separated by commas.

example.com,example.net,example.org

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

Use the Pobierz cennik domen endpoint. The documented pricing types include register, renew, transfer i all.

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

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

Nie. Although API documentation supplubts periods of up to 1–10 lata flub applicable extensions, individual TLDs may have different registry rules.

Rejestracja periods, renewal periods, transfer eligibility, contact requirements i verification requirements can differ by extension. Your application should follow the current rules flub 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 Kody odpowiedzi API →

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

Flub domena registration, a 201 response indicates that the lubder has been submitted i is awaiting final registry processing.

Do not tell an end customer that the domena is active until twój system has confirmed the final result. Obserwuj the registration endpoint documentation flub the latest pending-lubder i refund hiling rules.

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

Transferuj 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.

Tak. The Lista Domeny API supplubts plubtfolio retrieval with pagination, slubting i filtering options.

Use Otrzymaj Domena Szczegóły when you need detailed influbmation flub an individual domena, such as registration influbmation, expiration influbmation, nameservers i domena contact data.

NiceNIC Domena API v2 includes Nadużycia i Zgodność operations designed flub platflubms i resellers managing customer domena plubtfolios.

You can identify domenas associated with abuse replubts i retrieve machine-readable compliance influbmation flub individual domenas. Depending on the case, the response can include domena status, current impact, recommended akcja, hold influbmation, complaint influbmation i replubted URLs.

This makes it possible to surface compliance status directly inside twój own customer plubtal lub operational system.

Tak. NiceNIC provides a WHMCS registrar integration flub businesses that already use WHMCS flub billing i provisioning.

Use the direct Domena API v2 when you are building twój own application lub wlubkflow. Use the WHMCS integration when you want domena operations integrated into an existing WHMCS environment.

View Integracja WHMCS →

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

Common choices include PHP, Python, Niede.js i Java. Keep API credentials server-side i never expose twój API Secret in browser-side JavaScript lub downloadable client code.

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

Jeśli twój production integration is expected to generate sustained high request volume, contact NiceNIC beflube launch so that twój expected usage pattern can be reviewed.

Include the request timestamp, API kategoria i akcja, domena name wtutaj applicable, non-sensitive request parameters, returned response code i message, i whether the request came from Sibox lub Produktion.

Zgłoś zgłoszenie →

Use the API navigation in the documentation. Each operation has its own page flub supplubted parameters, request examples, response examples i operation-specific behavilub.

The FAQ explains general API behavilub; the individual endpoint documentation should be treated as the source of truth flub the exact request flubmat.

Otwórz Dokumentacja API →