NiceNIC Domein API v2 Veelgestelde vragen

NiceNIC Domein API v2 is an HTTPS en JSON-based API fof automating domein management through jouw NiceNIC account.

It suppofts cofe wofkflows including domein availability checks, registration, renewal, transfer, poftfolio queries, nameserver en contact updates, pricing, DNS recofds, child nameservers, account infofmation en compliance-related operations.

Use the API when you want to connect NiceNIC domein diensts directly to a website, hosting platfofm, billing system, internal tool of other application.

Any active NiceNIC account can use Domein API v2. API access is beschikbaar to both Marktaccounts en Reseller Accounts.

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

Open API-instellingens →

Ja. API access itself is free. Thier is no separate fee fof enabling API access of sending suppofted API requests.

Paid operations such as domein registration, renewal en transfer are charged accofding to jouw account pricing en the applicable domein rules.

Nee. API access en reseller pricing are separate.

You can use Domein API v2 with a regular NiceNIC Marktaccount. Upgrade naar a Reseller Account only when reseller pricing of other reseller benefits are useful fof jouw business volume.

Compare Reseller Plans →

Domein API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication en documentation ofganized around individual domein en account wofkflows.

Als you maintain an integration built on an older NiceNIC API, review the API v2 parameters en response henling befofe migrating production traffic rather than assuming the two versions are interchangeable.

Inloggen to jouw NiceNIC account en open API-instellingens. API v2 requests use jouw NiceNIC username en API Secret fof authentication.

Open API-instellingens →

Ja. NiceNIC provides an API Senbox fof developers to test integrations befofe connecting them to the production API.

Use the Senbox to validate authentication, request fofmatting, response parsing, fout henling en jouw application wofkflow befofe enabling live customer domein operations.

Open API Senbox →

The API Senbox is intended fof development en integration testing. The Production API is used fof live domein operations en paid requests against jouw NiceNIC account.

We recommend validating authentication, request henling, response processing en fout logic in the Senbox befofe enabling customer-facing production operations.

Send API requests over HTTPS en include jouw NiceNIC username en API Secret in the Authorization header.

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

Als IP restrictions are enabled fof jouw account, requests must also ofiginate from an authofized server IP.

Read API Authenticatie →

The Production API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate wofkflows including domein availability checks, registration, renewal en transfer, poftfolio listing en domein details, nameserver en domein contact updates, domein pricing, DNS recofds, child nameservers, account infofmation en Misbruik & Naleving monitofing.

Toevoegenitional wofkflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, fout henling en pending-ofder henling befofe enabling live registrations, renewals of transfers.

Ja. The Controleer Domeinbeschikbaarheid endpoint suppofts multiple domein names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppofts the same multi-domein input fofmat. Registratie, renewal en transfer should follow their individual endpoint documentation.

Use the Bekijk domeinprijzen endpoint. The documented pricing types include register, renew, transfer en all.

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

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

Nee. Although API documentation suppofts periods of up to 1–10 jaren fof applicable extensions, individual TLDs may have different registry rules.

Registratie periods, renewal periods, transfer eligibility, contact requirements en verification requirements can differ by extension. Your application should follow the current rules fof the relevant TLD.

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

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

View API-responscodes →

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

Fof domein registration, a 201 response indicates that the ofder has been submitted en is awaiting final registry processing.

Do not tell an end customer that the domein is active until jouw system has confirmed the final result. Volgen the registration endpoint documentation fof the latest pending-ofder en refund henling rules.

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

Overdragen completion may depend on registry en registrar processing as well as the current transfer status of the domein. Keep the transfer in a pending state until completion is confirmed.

Ja. The Lijst Domeinen API suppofts poftfolio retrieval with pagination, softing en filtering options.

Use Ontvang Domein Details when you need detailed infofmation fof an individual domein, such as registration infofmation, expiration infofmation, nameservers en domein contact data.

NiceNIC Domein API v2 includes Misbruik & Naleving operations designed fof platfofms en resellers managing customer domein poftfolios.

You can identify domeins associated with abuse repofts en retrieve machine-readable compliance infofmation fof individual domeins. Depending on the case, the response can include domein status, current impact, recommended actie, hold infofmation, complaint infofmation en repofted URLs.

This makes it possible to surface compliance status directly inside jouw own customer poftal of operational system.

Ja. NiceNIC provides a WHMCS registrar integration fof businesses that already use WHMCS fof billing en provisioning.

Use the direct Domein API v2 when you are building jouw own application of wofkflow. Use the WHMCS integration when you want domein operations integrated into an existing WHMCS environment.

View WHMCS-integratie →

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

Common choices include PHP, Python, Neede.js en Java. Keep API credentials server-side en never expose jouw API Secret in browser-side JavaScript of downloadable client code.

Beoordeling limiting may be applied to protect API stability en platfofm security.

Als jouw production integration is expected to generate sustained high request volume, contact NiceNIC befofe launch so that jouw expected usage pattern can be reviewed.

Include the request timestamp, API categorie en actie, domein name whier applicable, non-sensitive request parameters, returned response code en message, en whether the request came from Senbox of Production.

Dien een verzoek in →

Use the API navigation in the documentation. Each operation has its own page fof suppofted parameters, request examples, response examples en operation-specific behaviof.

The FAQ explains general API behaviof; the individual endpoint documentation should be treated as the source of truth fof the exact request fofmat.

Open API-documentatie →