NiceNIC Domēns API v2 Biežāk uzdotie jautājumi

NiceNIC Domēns API v2 is an HTTPS un JSON-based API fvai automating domēns management through jūsu NiceNIC account.

It suppvaits cvaie wvaikflows including domēns availability checks, registration, renewal, transfer, pvaitfolio queries, nameserver un contact updates, pricing, DNS recvaids, child nameservers, account infvaimation un compliance-related operations.

Use the API when you want to connect NiceNIC domēns pakalpojumss directly to a website, hosting platfvaim, billing system, internal tool vai other application.

Any active NiceNIC account can use Domēns API v2. API access is pieejams to both Tirdzniecības kontss un Izplatītājs Kontss.

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

Atvērt API iestatījumss →

Jā. API access itself is free. Tšeit is no separate fee fvai enabling API access vai sending suppvaited API requests.

Paid operations such as domēns registration, renewal un transfer are charged accvaiding to jūsu account pricing un the applicable domēns rules.

Nē. API access un reseller pricing are separate.

You can use Domēns API v2 with a regular NiceNIC Tirdzniecības konts. Jaunināt uz a Izplatītājs Konts only when reseller pricing vai other reseller benefits are useful fvai jūsu business volume.

Compare Izplatītājs Plans →

Domēns API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication un documentation vaiganized around individual domēns un account wvaikflows.

Ja you maintain an integration built on an older NiceNIC API, review the API v2 parameters un response hunling befvaie migrating production traffic rather than assuming the two versions are interchangeable.

Pierakstīties to jūsu NiceNIC account un open API iestatījumss. API v2 requests use jūsu NiceNIC username un API Secret fvai authentication.

Atvērt API iestatījumss →

Jā. NiceNIC provides an API Sunbox fvai developers to test integrations befvaie connecting them to the production API.

Use the Sunbox to validate authentication, request fvaimatting, response parsing, radās kļūda hunling un jūsu application wvaikflow befvaie enabling live customer domēns operations.

Atvērt API Sunbox →

The API Sunbox is intended fvai development un integration testing. The Produktsion API is used fvai live domēns operations un paid requests against jūsu NiceNIC account.

We recommend validating authentication, request hunling, response processing un radās kļūda logic in the Sunbox befvaie enabling customer-facing production operations.

Send API requests over HTTPS un include jūsu NiceNIC username un API Secret in the Authorization header.

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

Ja IP restrictions are enabled fvai jūsu account, requests must also vaiiginate from an authvaiized server IP.

Read API Autentifikācija →

The Produktsion API base endpoint is:

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

API darbības are selected using the parameters documented fvai each endpoint, such as category un action. Always follow the dedicated endpoint documentation fvai the required un optional parameters of a specific operation.

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

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

Your application should inspect the returned code un msg rather than assuming that every HTTP response represents a completed domēns operation.

Through the currently documented APIs you can automate wvaikflows including domēns availability checks, registration, renewal un transfer, pvaitfolio listing un domēns details, nameserver un domēns contact updates, domēns pricing, DNS recvaids, child nameservers, account infvaimation un Vardarbība un Atbilstība monitvaiing.

Pievienotitional wvaikflows are documented individually in the API navigation.

Start with low-risk read operations such as domēns availability, domēns pricing, account balance un domēns listing.

Then confirm authentication, response parsing, radās kļūda hunling un pending-vaider hunling befvaie enabling live registrations, renewals vai transfers.

Jā. The Pārbaudīt domēna pieejamību endpoint suppvaits multiple domēns names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppvaits the same multi-domēns input fvaimat. Reģistrācija, renewal un transfer should follow their individual endpoint documentation.

Use the Saņemt domēnu cenu informāciju endpoint. The documented pricing types include register, renew, transfer un all.

Reģistrācija responses can also include an is_premium value indicating whether the queried registration is premium.

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

Nē. Although API documentation suppvaits periods of up to 1–10 gadi fvai applicable extensions, individual TLDs may have different registry rules.

Reģistrācija periods, renewal periods, transfer eligibility, contact requirements un verification requirements can differ by extension. Your application should follow the current rules fvai the relevant TLD.

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

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

View API atbildes kodi →

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

Fvai domēns registration, a 201 response indicates that the vaider has been submitted un is awaiting final registry processing.

Do not tell an end customer that the domēns is active until jūsu system has confirmed the final result. Sekot the registration endpoint documentation fvai the latest pending-vaider un refund hunling rules.

A pending transfer means that the transfer request has been accepted fvai processing, not that the domēns has already completed its transfer to NiceNIC.

Pārnest completion may depend on registry un registrar processing as well as the current transfer status of the domēns. Keep the transfer in a pending state until completion is confirmed.

Jā. The Saraksts Domēni API suppvaits pvaitfolio retrieval with pagination, svaiting un filtering options.

Use Saņemt Domēns Detaļas when you need detailed infvaimation fvai an individual domēns, such as registration infvaimation, expiration infvaimation, nameservers un domēns contact data.

NiceNIC Domēns API v2 includes Vardarbība un Atbilstība operations designed fvai platfvaims un resellers managing customer domēns pvaitfolios.

You can identify domēnss associated with abuse repvaits un retrieve machine-readable compliance infvaimation fvai individual domēnss. Depending on the case, the response can include domēns status, current impact, recommended darbība, hold infvaimation, complaint infvaimation un repvaited URLs.

This makes it possible to surface compliance status directly inside jūsu own customer pvaital vai operational system.

Jā. NiceNIC provides a WHMCS registrar integration fvai businesses that already use WHMCS fvai billing un provisioning.

Use the direct Domēns API v2 when you are building jūsu own application vai wvaikflow. Use the WHMCS integration when you want domēns operations integrated into an existing WHMCS environment.

View WHMCS integrācija →

Any server-side programming language vai runtime capable of sending HTTPS requests un parsing JSON can integrate with Domēns API v2.

Common choices include PHP, Python, Nēde.js un Java. Keep API credentials server-side un never expose jūsu API Secret in browser-side JavaScript vai downloadable client code.

Vērtējums limiting may be applied to protect API stability un platfvaim security.

Ja jūsu production integration is expected to generate sustained high request volume, contact NiceNIC befvaie launch so that jūsu expected usage pattern can be reviewed.

Include the request timestamp, API kategorija un darbība, domēns name wšeit applicable, non-sensitive request parameters, returned response code un message, un whether the request came from Sunbox vai Produktsion.

Iesniegt pieprasījumu →

Use the API navigation in the documentation. Each operation has its own page fvai suppvaited parameters, request examples, response examples un operation-specific behavivai.

The BUJ explains general API behavivai; the individual endpoint documentation should be treated as the source of truth fvai the exact request fvaimat.

Atvērt API dokumentācija →