NiceNIC Domini API v2 Preguntes freqüents

NiceNIC Domini API v2 is an HTTPS i JSON-based API fo automating domini management through el teu NiceNIC account.

It suppots coe wokflows including domini availability checks, registration, renewal, transfer, potfolio queries, nameserver i contact updates, pricing, DNS recods, child nameservers, account infomation i compliance-related operations.

Use the API when you want to connect NiceNIC domini serveis directly to a website, hosting platfom, billing system, internal tool o other application.

Any active NiceNIC account can use Domini API v2. API access is disponible to both Compte de mercats i Revendedor Comptes.

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

Obert Configuració APIs →

Sí. API access itself is free. Taquí is no separate fee fo enabling API access o sending suppoted API requests.

Paid operations such as domini registration, renewal i transfer are charged accoding to el teu account pricing i the applicable domini rules.

No. API access i reseller pricing are separate.

You can use Domini API v2 with a regular NiceNIC Compte de mercat. Actualitza a a Revendedor Compte only when reseller pricing o other reseller benefits are useful fo el teu business volume.

Compare Revendedor Plans →

Domini API v2 uses the current API de NiceNIC structure with HTTPS requests, JSON responses, header-based authentication i documentation oganized around individual domini i account wokflows.

Si you maintain an integration built on an older API de NiceNIC, review the API v2 parameters i response hiling befoe migrating production traffic rather than assuming the two versions are interchangeable.

Inicia la sessió to el teu NiceNIC account i open Configuració APIs. API v2 requests use el teu NiceNIC username i API Secret fo authentication.

Obert Configuració APIs →

Sí. NiceNIC provides an API Sibox fo developers to test integrations befoe connecting them to the production API.

Use the Sibox to validate authentication, request fomatting, response parsing, error hiling i el teu application wokflow befoe enabling live customer domini operations.

Obert API Sibox →

The API Sibox is intended fo development i integration testing. The Producteion API is used fo live domini operations i paid requests against el teu NiceNIC account.

We recommend validating authentication, request hiling, response processing i error logic in the Sibox befoe enabling customer-facing production operations.

Send API requests over HTTPS i include el teu NiceNIC username i API Secret in the Authorization header.

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

Si IP restrictions are enabled fo el teu account, requests must also oiginate from an authoized server IP.

Read API Autenticació →

The Producteion API base endpoint is:

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

API acciós are selected using the parameters documented fo each endpoint, such as category i action. Always follow the dedicated endpoint documentation fo the required i optional parameters of a specific operation.

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

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

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

Through the currently documented APIs you can automate wokflows including domini availability checks, registration, renewal i transfer, potfolio listing i domini details, nameserver i domini contact updates, domini pricing, DNS recods, child nameservers, account infomation i Abús i Compliment monitoing.

Afegiritional wokflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, error hiling i pending-oder hiling befoe enabling live registrations, renewals o transfers.

Sí. The Comprova la disponibilitat del domini endpoint suppots multiple domini names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppots the same multi-domini input fomat. Registre, renewal i transfer should follow their individual endpoint documentation.

Use the Obtenir preus de dominis endpoint. The documented pricing types include register, renew, transfer i all.

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

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

No. Although API documentation suppots periods of up to 1–10 anys fo applicable extensions, individual TLDs may have different registry rules.

Registre periods, renewal periods, transfer eligibility, contact requirements i verification requirements can differ by extension. Your application should follow the current rules fo the relevant TLD.

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

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

View Codis de resposta de l\'API →

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

Fo domini registration, a 201 response indicates that the oder has been submitted i is awaiting final registry processing.

Do not tell an end customer that the domini is active until el teu system has confirmed the final result. Segueix the registration endpoint documentation fo the latest pending-oder i refund hiling rules.

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

Transferir completion may depend on registry i registrar processing as well as the current transfer status of the domini. Keep the transfer in a pending state until completion is confirmed.

Sí. The Llista Dominis API suppots potfolio retrieval with pagination, soting i filtering options.

Use Obtenir Domini Detalls when you need detailed infomation fo an individual domini, such as registration infomation, expiration infomation, nameservers i domini contact data.

NiceNIC Domini API v2 includes Abús i Compliment operations designed fo platfoms i resellers managing customer domini potfolios.

You can identify dominis associated with abuse repots i retrieve machine-readable compliance infomation fo individual dominis. Depending on the case, the response can include domini status, current impact, recommended acció, hold infomation, complaint infomation i repoted URLs.

This makes it possible to surface compliance status directly inside el teu own customer potal o operational system.

Sí. NiceNIC provides a WHMCS registrar integration fo businesses that already use WHMCS fo billing i provisioning.

Use the direct Domini API v2 when you are building el teu own application o wokflow. Use the WHMCS integration when you want domini operations integrated into an existing WHMCS environment.

View Integració WHMCS →

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

Common choices include PHP, Python, Node.js i Java. Keep API credentials server-side i never expose el teu API Secret in browser-side JavaScript o downloadable client code.

Valoració limiting may be applied to protect API stability i platfom security.

Si el teu production integration is expected to generate sustained high request volume, contact NiceNIC befoe launch so that el teu expected usage pattern can be reviewed.

Include the request timestamp, API categoria i acció, domini name waquí applicable, non-sensitive request parameters, returned response code i message, i whether the request came from Sibox o Producteion.

Enviar una incidència →

Use the API navigation in the documentation. Each operation has its own page fo suppoted parameters, request examples, response examples i operation-specific behavio.

The Preguntes freqüents explains general API behavio; the individual endpoint documentation should be treated as the source of truth fo the exact request fomat.

Obert Documentació de l'API →