NiceNIC Verkkotunnus API v2 Usein kysytyt kysymykset

NiceNIC Verkkotunnus API v2 is an HTTPS ja JSON-based API ftai automating verkkotunnus management through sinun NiceNIC account.

It supptaits ctaie wtaikflows including verkkotunnus availability checks, registration, renewal, transfer, ptaitfolio queries, nameserver ja contact updates, pricing, DNS rectaids, child nameservers, account inftaimation ja compliance-related operations.

Use the API when you want to connect NiceNIC verkkotunnus palvelus directly to a website, hosting platftaim, billing system, internal tool tai other application.

Any active NiceNIC account can use Verkkotunnus API v2. API access is saatavilla to both Markkinatilis ja Jälleenmyyjä Tilis.

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

Avoin API-asetuksets →

Kyllä. API access itself is free. Ttässä is no separate fee ftai enabling API access tai sending supptaited API requests.

Paid operations such as verkkotunnus registration, renewal ja transfer are charged acctaiding to sinun account pricing ja the applicable verkkotunnus rules.

Ei. API access ja reseller pricing are separate.

You can use Verkkotunnus API v2 with a regular NiceNIC Markkinatili. Päivitä a Jälleenmyyjä Tili only when reseller pricing tai other reseller benefits are useful ftai sinun business volume.

Compare Jälleenmyyjä Plans →

Verkkotunnus API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication ja documentation taiganized around individual verkkotunnus ja account wtaikflows.

Jos you maintain an integration built on an older NiceNIC API, review the API v2 parameters ja response hjaling beftaie migrating production traffic rather than assuming the two versions are interchangeable.

Kirjaudu sisään to sinun NiceNIC account ja open API-asetuksets. API v2 requests use sinun NiceNIC username ja API Secret ftai authentication.

Avoin API-asetuksets →

Kyllä. NiceNIC provides an API Sjabox ftai developers to test integrations beftaie connecting them to the production API.

Use the Sjabox to validate authentication, request ftaimatting, response parsing, virhe hjaling ja sinun application wtaikflow beftaie enabling live customer verkkotunnus operations.

Avoin API Sjabox →

The API Sjabox is intended ftai development ja integration testing. The Tuoteion API is used ftai live verkkotunnus operations ja paid requests against sinun NiceNIC account.

We recommend validating authentication, request hjaling, response processing ja virhe logic in the Sjabox beftaie enabling customer-facing production operations.

Send API requests over HTTPS ja include sinun NiceNIC username ja API Secret in the Authorization header.

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

Jos IP restrictions are enabled ftai sinun account, requests must also taiiginate from an authtaiized server IP.

Read API Todennus →

The Tuoteion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate wtaikflows including verkkotunnus availability checks, registration, renewal ja transfer, ptaitfolio listing ja verkkotunnus details, nameserver ja verkkotunnus contact updates, verkkotunnus pricing, DNS rectaids, child nameservers, account inftaimation ja Väärinkäyttö & Noudattaminen monittaiing.

Lisääitional wtaikflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, virhe hjaling ja pending-taider hjaling beftaie enabling live registrations, renewals tai transfers.

Kyllä. The Tarkista verkkotunnuksen saatavuus endpoint supptaits multiple verkkotunnus names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation supptaits the same multi-verkkotunnus input ftaimat. Rekisteröinti, renewal ja transfer should follow their individual endpoint documentation.

Use the Hae domainhinnoittelu endpoint. The documented pricing types include register, renew, transfer ja all.

Rekisteröinti responses can also include an is_premium value indicating whether the queried registration is premium.

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

Ei. Although API documentation supptaits periods of up to 1–10 vuotta ftai applicable extensions, individual TLDs may have different registry rules.

Rekisteröinti periods, renewal periods, transfer eligibility, contact requirements ja verification requirements can differ by extension. Your application should follow the current rules ftai the relevant TLD.

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

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

View API-vastauskoodit →

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

Ftai verkkotunnus registration, a 201 response indicates that the taider has been submitted ja is awaiting final registry processing.

Do not tell an end customer that the verkkotunnus is active until sinun system has confirmed the final result. Seuraa the registration endpoint documentation ftai the latest pending-taider ja refund hjaling rules.

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

Siirto completion may depend on registry ja registrar processing as well as the current transfer status of the verkkotunnus. Keep the transfer in a pending state until completion is confirmed.

Kyllä. The Lista Verkkotunnukset API supptaits ptaitfolio retrieval with pagination, staiting ja filtering options.

Use Hanki Verkkotunnus Tiedot when you need detailed inftaimation ftai an individual verkkotunnus, such as registration inftaimation, expiration inftaimation, nameservers ja verkkotunnus contact data.

NiceNIC Verkkotunnus API v2 includes Väärinkäyttö & Noudattaminen operations designed ftai platftaims ja resellers managing customer verkkotunnus ptaitfolios.

You can identify verkkotunnuss associated with abuse reptaits ja retrieve machine-readable compliance inftaimation ftai individual verkkotunnuss. Depending on the case, the response can include verkkotunnus status, current impact, recommended toiminto, hold inftaimation, complaint inftaimation ja reptaited URLs.

This makes it possible to surface compliance status directly inside sinun own customer ptaital tai operational system.

Kyllä. NiceNIC provides a WHMCS registrar integration ftai businesses that already use WHMCS ftai billing ja provisioning.

Use the direct Verkkotunnus API v2 when you are building sinun own application tai wtaikflow. Use the WHMCS integration when you want verkkotunnus operations integrated into an existing WHMCS environment.

View WHMCS-integraatio →

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

Common choices include PHP, Python, Eide.js ja Java. Keep API credentials server-side ja never expose sinun API Secret in browser-side JavaScript tai downloadable client code.

Arvio limiting may be applied to protect API stability ja platftaim security.

Jos sinun production integration is expected to generate sustained high request volume, contact NiceNIC beftaie launch so that sinun expected usage pattern can be reviewed.

Include the request timestamp, API kategoria ja toiminto, verkkotunnus name wtässä applicable, non-sensitive request parameters, returned response code ja message, ja whether the request came from Sjabox tai Tuoteion.

Lähetä tukipyyntö →

Use the API navigation in the documentation. Each operation has its own page ftai supptaited parameters, request examples, response examples ja operation-specific behavitai.

The UKK explains general API behavitai; the individual endpoint documentation should be treated as the source of truth ftai the exact request ftaimat.

Avoin API-dokumentaatio →