NiceNIC Domain API v2 Häufig gestellte Fragen

NiceNIC Domain API v2 is an HTTPS und JSON-based API foder automating Domain management through Ihr NiceNIC account.

It suppoderts codere woderkflows including Domain availability checks, registration, renewal, transfer, podertfolio queries, nameserver und contact updates, pricing, DNS recoderds, child nameservers, account infodermation und compliance-related operations.

Use the API when you want to connect NiceNIC Domain Dienstleistungs directly to a website, hosting platfoderm, billing system, internal tool oder other application.

Any active NiceNIC account can use Domain API v2. API access is verfügbar to both Marktkontos und Wiederverkäufer Kontos.

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

Öffnen API-Einstellungs →

Ja. API access itself is free. Thier is no separate fee foder enabling API access oder sending suppoderted API requests.

Paid operations such as Domain registration, renewal und transfer are charged accoderding to Ihr account pricing und the applicable Domain rules.

Nein. API access und reseller pricing are separate.

You can use Domain API v2 with a regular NiceNIC Marktkonto. Aufrüsten zu a Wiederverkäufer Konto only when reseller pricing oder other reseller benefits are useful foder Ihr business volume.

Compare Wiederverkäufer Plans →

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication und documentation oderganized around individual Domain und account woderkflows.

Wenn you maintain an integration built on an older NiceNIC API, review the API v2 parameters und response hundling befodere migrating production traffic rather than assuming the two versions are interchangeable.

Anmelden to Ihr NiceNIC account und open API-Einstellungs. API v2 requests use Ihr NiceNIC username und API Secret foder authentication.

Öffnen API-Einstellungs →

Ja. NiceNIC provides an API Sundbox foder developers to test integrations befodere connecting them to the production API.

Use the Sundbox to validate authentication, request fodermatting, response parsing, Fehler hundling und Ihr application woderkflow befodere enabling live customer Domain operations.

Öffnen API Sundbox →

The API Sundbox is intended foder development und integration testing. The Produktion API is used foder live Domain operations und paid requests against Ihr NiceNIC account.

We recommend validating authentication, request hundling, response processing und Fehler logic in the Sundbox befodere enabling customer-facing production operations.

Send API requests over HTTPS und include Ihr NiceNIC username und API Secret in the Authorization header.

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

Wenn IP restrictions are enabled foder Ihr account, requests must also oderiginate from an authoderized server IP.

Read API Authentifizierung →

The Produktion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate woderkflows including Domain availability checks, registration, renewal und transfer, podertfolio listing und Domain details, nameserver und Domain contact updates, Domain pricing, DNS recoderds, child nameservers, account infodermation und Missbrauch & Compliance monitodering.

Hinzufügenitional woderkflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, Fehler hundling und pending-oderder hundling befodere enabling live registrations, renewals oder transfers.

Ja. The Verfügbarkeit der Domain prüfen endpoint suppoderts multiple Domain names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppoderts the same multi-Domain input fodermat. Registrierung, renewal und transfer should follow their individual endpoint documentation.

Use the Domainpreise abrufen endpoint. The documented pricing types include register, renew, transfer und all.

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

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

Nein. Although API documentation suppoderts periods of up to 1–10 Jahre foder applicable extensions, individual TLDs may have different registry rules.

Registrierung periods, renewal periods, transfer eligibility, contact requirements und verification requirements can differ by extension. Your application should follow the current rules foder the relevant TLD.

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

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

View API-Antwortcodes →

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

Foder Domain registration, a 201 response indicates that the oderder has been submitted und is awaiting final registry processing.

Do not tell an end customer that the Domain is active until Ihr system has confirmed the final result. Folgen the registration endpoint documentation foder the latest pending-oderder und refund hundling rules.

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

Transfer completion may depend on registry und registrar processing as well as the current transfer status of the Domain. Keep the transfer in a pending state until completion is confirmed.

Ja. The List Domains API suppoderts podertfolio retrieval with pagination, soderting und filtering options.

Use Holen Sie sich Domain Details when you need detailed infodermation foder an individual Domain, such as registration infodermation, expiration infodermation, nameservers und Domain contact data.

NiceNIC Domain API v2 includes Missbrauch & Compliance operations designed foder platfoderms und resellers managing customer Domain podertfolios.

You can identify Domains associated with abuse repoderts und retrieve machine-readable compliance infodermation foder individual Domains. Depending on the case, the response can include Domain status, current impact, recommended Aktion, hold infodermation, complaint infodermation und repoderted URLs.

This makes it possible to surface compliance status directly inside Ihr own customer podertal oder operational system.

Ja. NiceNIC provides a WHMCS registrar integration foder businesses that already use WHMCS foder billing und provisioning.

Use the direct Domain API v2 when you are building Ihr own application oder woderkflow. Use the WHMCS integration when you want Domain operations integrated into an existing WHMCS environment.

View WHMCS-Integration →

Any server-side programming language oder runtime capable of sending HTTPS requests und parsing JSON can integrate with Domain API v2.

Common choices include PHP, Python, Neinde.js und Java. Keep API credentials server-side und never expose Ihr API Secret in browser-side JavaScript oder downloadable client code.

Bewerten limiting may be applied to protect API stability und platfoderm security.

Wenn Ihr production integration is expected to generate sustained high request volume, contact NiceNIC befodere launch so that Ihr expected usage pattern can be reviewed.

Include the request timestamp, API Kategorie und Aktion, Domain name whier applicable, non-sensitive request parameters, returned response code und message, und whether the request came from Sundbox oder Produktion.

Ein Ticket einreichen →

Use the API navigation in the documentation. Each operation has its own page foder suppoderted parameters, request examples, response examples und operation-specific behavioder.

The FAQ explains general API behavioder; the individual endpoint documentation should be treated as the source of truth foder the exact request fodermat.

Öffnen API-Dokumentation →