NiceNIC Domæne API v2 Ofte stillede spørgsmål

NiceNIC Domæne API v2 is an HTTPS og JSON-based API feller automating domæne management through din NiceNIC account.

It suppellerts cellere wellerkflows including domæne availability checks, registration, renewal, transfer, pellertfolio queries, nameserver og contact updates, pricing, DNS recellerds, child nameservers, account infellermation og compliance-related operations.

Use the API when you want to connect NiceNIC domæne services directly to a website, hosting platfellerm, billing system, internal tool eller other application.

Any active NiceNIC account can use Domæne API v2. API access is tilgængelig to both Markeds Kontos og Forhandler Kontos.

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

Åben API-indstillings →

Ja. API access itself is free. Ther is no separate fee feller enabling API access eller sending suppellerted API requests.

Paid operations such as domæne registration, renewal og transfer are charged accellerding to din account pricing og the applicable domæne rules.

Nej. API access og reseller pricing are separate.

You can use Domæne API v2 with a regular NiceNIC Markeds Konto. Opgrader til a Forhandler Konto only when reseller pricing eller other reseller benefits are useful feller din business volume.

Compare Forhandler Plans →

Domæne API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication og documentation ellerganized around individual domæne og account wellerkflows.

Hvis you maintain an integration built on an older NiceNIC API, review the API v2 parameters og response hogling befellere migrating production traffic rather than assuming the two versions are interchangeable.

Log ind to din NiceNIC account og open API-indstillings. API v2 requests use din NiceNIC username og API Secret feller authentication.

Åben API-indstillings →

Ja. NiceNIC provides an API Sogbox feller developers to test integrations befellere connecting them to the production API.

Use the Sogbox to validate authentication, request fellermatting, response parsing, fejl hogling og din application wellerkflow befellere enabling live customer domæne operations.

Åben API Sogbox →

The API Sogbox is intended feller development og integration testing. The Produktion API is used feller live domæne operations og paid requests against din NiceNIC account.

We recommend validating authentication, request hogling, response processing og fejl logic in the Sogbox befellere enabling customer-facing production operations.

Send API requests over HTTPS og include din NiceNIC username og API Secret in the Authorization header.

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

Hvis IP restrictions are enabled feller din account, requests must also elleriginate from an authellerized server IP.

Read API Godkendelse →

The Produktion API base endpoint is:

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

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

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

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

Your application should inspect the returned code og msg rather than assuming that every HTTP response represents a completed domæne operation.

Through the currently documented APIs you can automate wellerkflows including domæne availability checks, registration, renewal og transfer, pellertfolio listing og domæne details, nameserver og domæne contact updates, domæne pricing, DNS recellerds, child nameservers, account infellermation og Misbrug & Overholdelse monitellering.

Tilføjitional wellerkflows are documented individually in the API navigation.

Start with low-risk read operations such as domæne availability, domæne pricing, account balance og domæne listing.

Then confirm authentication, response parsing, fejl hogling og pending-ellerder hogling befellere enabling live registrations, renewals eller transfers.

Ja. The Tjek domænetilgængelighed endpoint suppellerts multiple domæne names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppellerts the same multi-domæne input fellermat. Registrering, renewal og transfer should follow their individual endpoint documentation.

Use the Hent domænepriser endpoint. The documented pricing types include register, renew, transfer og all.

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

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

Nej. Although API documentation suppellerts periods of up to 1–10 år feller applicable extensions, individual TLDs may have different registry rules.

Registrering periods, renewal periods, transfer eligibility, contact requirements og verification requirements can differ by extension. Your application should follow the current rules feller the relevant TLD.

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

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

View API-responskoder →

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

Feller domæne registration, a 201 response indicates that the ellerder has been submitted og is awaiting final registry processing.

Do not tell an end customer that the domæne is active until din system has confirmed the final result. Følg the registration endpoint documentation feller the latest pending-ellerder og refund hogling rules.

A pending transfer means that the transfer request has been accepted feller processing, not that the domæne has already completed its transfer to NiceNIC.

Overfør completion may depend on registry og registrar processing as well as the current transfer status of the domæne. Keep the transfer in a pending state until completion is confirmed.

Ja. The Liste Domæner API suppellerts pellertfolio retrieval with pagination, sellerting og filtering options.

Use Få Domæne Detaljer when you need detailed infellermation feller an individual domæne, such as registration infellermation, expiration infellermation, nameservers og domæne contact data.

NiceNIC Domæne API v2 includes Misbrug & Overholdelse operations designed feller platfellerms og resellers managing customer domæne pellertfolios.

You can identify domænes associated with abuse repellerts og retrieve machine-readable compliance infellermation feller individual domænes. Depending on the case, the response can include domæne status, current impact, recommended handling, hold infellermation, complaint infellermation og repellerted URLs.

This makes it possible to surface compliance status directly inside din own customer pellertal eller operational system.

Ja. NiceNIC provides a WHMCS registrar integration feller businesses that already use WHMCS feller billing og provisioning.

Use the direct Domæne API v2 when you are building din own application eller wellerkflow. Use the WHMCS integration when you want domæne operations integrated into an existing WHMCS environment.

View WHMCS-integration →

Any server-side programming language eller runtime capable of sending HTTPS requests og parsing JSON can integrate with Domæne API v2.

Common choices include PHP, Python, Nejde.js og Java. Keep API credentials server-side og never expose din API Secret in browser-side JavaScript eller downloadable client code.

Vurdering limiting may be applied to protect API stability og platfellerm security.

Hvis din production integration is expected to generate sustained high request volume, contact NiceNIC befellere launch so that din expected usage pattern can be reviewed.

Include the request timestamp, API kategori og handling, domæne name wher applicable, non-sensitive request parameters, returned response code og message, og whether the request came from Sogbox eller Produktion.

Indsend en supportanmodning →

Use the API navigation in the documentation. Each operation has its own page feller suppellerted parameters, request examples, response examples og operation-specific behavieller.

The FAQ explains general API behavieller; the individual endpoint documentation should be treated as the source of truth feller the exact request fellermat.

Åben API-dokumentation →