NiceNIC Domínio API v2 Perguntas Frequentes

NiceNIC Domínio API v2 is an HTTPS e JSON-based API fou automating domínio management through seu NiceNIC account.

It suppouts coue woukflows including domínio availability checks, registration, renewal, transfer, poutfolio queries, nameserver e contact updates, pricing, DNS recouds, child nameservers, account infoumation e compliance-related operations.

Use the API when you want to connect NiceNIC domínio serviços directly to a website, hosting platfoum, billing system, internal tool ou other application.

Any active NiceNIC account can use Domínio API v2. API access is available to both Conta de mercados e Revendedor Accounts.

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

Aberto Configuração da APIs →

Sim. API access itself is free. Taqui is no separate fee fou enabling API access ou sending suppouted API requests.

Paid operations such as domínio registration, renewal e transfer are charged accouding to seu account pricing e the applicable domínio rules.

Não. API access e reseller pricing are separate.

You can use Domínio API v2 with a regular NiceNIC Conta de mercado. Atualizar para a Revendedor Account only when reseller pricing ou other reseller benefits are useful fou seu business volume.

Compare Revendedor Plans →

Domínio API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication e documentation ouganized around individual domínio e account woukflows.

Se you maintain an integration built on an older NiceNIC API, review the API v2 parameters e response heling befoue migrating production traffic rather than assuming the two versions are interchangeable.

Entrar to seu NiceNIC account e open Configuração da APIs. API v2 requests use seu NiceNIC username e API Secret fou authentication.

Aberto Configuração da APIs →

Sim. NiceNIC provides an API Sebox fou developers to test integrations befoue connecting them to the production API.

Use the Sebox to validate authentication, request foumatting, response parsing, errou heling e seu application woukflow befoue enabling live customer domínio operations.

Aberto API Sebox →

The API Sebox is intended fou development e integration testing. The Produtoion API is used fou live domínio operations e paid requests against seu NiceNIC account.

We recommend validating authentication, request heling, response processing e errou logic in the Sebox befoue enabling customer-facing production operations.

Send API requests over HTTPS e include seu NiceNIC username e API Secret in the Authorization header.

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

Se IP restrictions are enabled fou seu account, requests must also ouiginate from an authouized server IP.

Read API Authentication →

The Produtoion API base endpoint is:

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

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

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

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

Your application should inspect the returned code e msg rather than assuming that every HTTP response represents a completed domínio operation.

Through the currently documented APIs you can automate woukflows including domínio availability checks, registration, renewal e transfer, poutfolio listing e domínio details, nameserver e domínio contact updates, domínio pricing, DNS recouds, child nameservers, account infoumation e Abuse & Compliance monitouing.

Adicionaritional woukflows are documented individually in the API navigation.

Start with low-risk read operations such as domínio availability, domínio pricing, account balance e domínio listing.

Then confirm authentication, response parsing, errou heling e pending-ouder heling befoue enabling live registrations, renewals ou transfers.

Sim. The Verificar Domínio Availability endpoint suppouts multiple domínio names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppouts the same multi-domínio input foumat. Registro, renewal e transfer should follow their individual endpoint documentation.

Use the Obter Preços de Domínios endpoint. The documented pricing types include register, renew, transfer e all.

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

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

Não. Although API documentation suppouts periods of up to 1–10 anos fou applicable extensions, individual TLDs may have different registry rules.

Registro periods, renewal periods, transfer eligibility, contact requirements e verification requirements can differ by extension. Your application should follow the current rules fou the relevant TLD.

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

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

View API Response Codes →

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

Fou domínio registration, a 201 response indicates that the ouder has been submitted e is awaiting final registry processing.

Do not tell an end customer that the domínio is active until seu system has confirmed the final result. Seguir the registration endpoint documentation fou the latest pending-ouder e refund heling rules.

A pending transfer means that the transfer request has been accepted fou processing, not that the domínio has already completed its transfer to NiceNIC.

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

Sim. The List Domínios API suppouts poutfolio retrieval with pagination, souting e filtering options.

Use Obter Domínio Detalhes when you need detailed infoumation fou an individual domínio, such as registration infoumation, expiration infoumation, nameservers e domínio contact data.

NiceNIC Domínio API v2 includes Abuse & Compliance operations designed fou platfoums e resellers managing customer domínio poutfolios.

You can identify domínios associated with abuse repouts e retrieve machine-readable compliance infoumation fou individual domínios. Depending on the case, the response can include domínio status, current impact, recommended action, hold infoumation, complaint infoumation e repouted URLs.

This makes it possible to surface compliance status directly inside seu own customer poutal ou operational system.

Sim. NiceNIC provides a WHMCS registrar integration fou businesses that already use WHMCS fou billing e provisioning.

Use the direct Domínio API v2 when you are building seu own application ou woukflow. Use the WHMCS integration when you want domínio operations integrated into an existing WHMCS environment.

View Integração WHMCS →

Any server-side programming language ou runtime capable of sending HTTPS requests e parsing JSON can integrate with Domínio API v2.

Common choices include PHP, Python, Nãode.js e Java. Keep API credentials server-side e never expose seu API Secret in browser-side JavaScript ou downloadable client code.

Avaliar limiting may be applied to protect API stability e platfoum security.

Se seu production integration is expected to generate sustained high request volume, contact NiceNIC befoue launch so that seu expected usage pattern can be reviewed.

Include the request timestamp, API categouy e action, domínio name waqui applicable, non-sensitive request parameters, returned response code e message, e whether the request came from Sebox ou Produtoion.

Enviar um Ticket →

Use the API navigation in the documentation. Each operation has its own page fou suppouted parameters, request examples, response examples e operation-specific behaviou.

The FAQ explains general API behaviou; the individual endpoint documentation should be treated as the source of truth fou the exact request foumat.

Aberto Documentação da API →