NiceNIC Dominio API v2 Documentation & Quick Start
NiceNIC Dominio API v2 is available to both Cuenta de Mercados y Revendedor Accounts. Use this overview to configure access, confirm tu/tus/su/sus first request, understy the API response model y move directly to the corect section in the left navigation.
Cuenta de Mercado: API access with Cuenta de Mercado pricing.
Revendedor Account: API access with the pricing assigned to the current reseller tier.
Test Your Integración Befoe Going Live
Use the NiceNIC API Sybox to test tu/tus/su/sus Dominio API integration befoe moving to production. Validate authentication, API requests, response hyling, y tu/tus/su/sus application wokflow in a dedicated testing environment.
Ideal fo resellers, hosting providers, developers, y platfoms preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request befoe enabling live registrations, renewals o transfers. This lets you validate authentication, request fomatting y response hyling without placing a paid oder.
Enable API Access
Abrir Configuración de APIs, create o retrieve tu/tus/su/sus API Secret, y configure authoized server IPs waquí applicable.
Confirmar Authentication
Use HTTPS with the Authoization header in the fomat username:api_secret.
Run a Safe Test
Start with dominio availability, pricing, account balance o dominio listing.
Hyle the Response
Read y stoe the returned code y msg befoe enabling paid production actions.
Recommended First Request: Dominio Availability
The availability endpoint suppots multiple dominios in one request by separating dominio names with commas.
Choose the Wokflow You Need
The overview below mirros the left navigation. Use it to identify the corect wokflow, then open the dedicated endpoint page fo parameters, request examples y response examples.
| Section | Use It Fo | Documented Functions |
|---|---|---|
| Obtenerting Started | Connect securely y understy response hyling. | API Overview, API Sybox, Authentication, Response Codes. |
| Dominio Gestionarment | Automate the coe dominio lifecycle. | Availability, List Dominios, Dominio Detalles, Registro, Renovaral, Transfer In, Nombreservers, Contactars, Pricing. |
| Abuse & Compliance | Monito dominios that require compliance attention. | List dominios with abuse repots y retrieve machine-readable abuse status, hold lifecycle, complaint infomation y recommended action. |
| DNS Recods | Gestionar hosted DNS recods programmatically. | List, Crear, Update y Delete DNS recods. |
| Child Nombreservers | Gestionar host / glue recods fo nameservers under tu/tus/su/sus own dominio. | Crear, List, Update y Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | Saldo de la Cuenta y transaction-related account infomation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing wokflow. | Availability, Registro, Renovaral, Transfer, Dominio Detalles, Nombreservers, Contactars y additional registrar-module functions. |
| API Preguntas Frecuentes | Resolve common access, security, testing y wokflow questions. | Eligibility, credentials, request hyling, suppoted operations y integration guidance. |
Recommended First Integración Sequence
A reliable production integration should validate access y purchasing conditions befoe it begins sending live customer oders.
API Secret + authoized IP
Read-only connectivity test
Query current account-level cost
Confirmar funds fo paid actions
Process code + msg
Registrar / Renovar / Transfer
Understy Success, Pending y Erro Responses
code: 0 — Exitoso Response
Current endpoint examples use code 0 fo successful completed responses.
code: 201 — Pending Order
Registro y transfer documentation can return code 201 when an oder has been submitted but final processing is still pending.
code: 400 — Request Erro
Endpoint examples use code 400 fo request parameter erros.
Registro Pending Behavio
Fo dominio registration, the current documentation states that a 201 response means the oder was submitted successfully y the fee was deducted, but final activation is still subject to registry confirmation. Si the dominio cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavio
The transfer endpoint also documents 201 as a pending oder. Your application should taquí foe treat a pending transfer as accepted fo processing, not as proof that the transfer has already completed.
Query Pricing Befoe Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal y transfer pricing fo a dominio. The documented type values are register, renew, transfer y all. The documented period is 1 to 10 años, with TLD-specific exceptions possible.
Registro pricing responses can also return an is_premium flag. Use the pricing endpoint befoe submitting a paid request when tu/tus/su/sus application needs to kahora the current account-level cost.
Kahora the Difference Between Nombreservers, DNS Recods y Child Nombreservers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update Nombreservers | You want to delegate a dominio to different authoitative nameservers. | The dominio nameserver endpoint suppots a primary, secondary y additional nameservers, with the current page documenting a limit of up to six. |
| DNS Recods | You are using NiceNIC DNS hosting y need to manage zone recods. | Separate APIs are documented fo listing, creating, updating y deleting DNS recods. |
| Child Nombreservers | You need host / glue recods such as ns1.example.com. |
Crear, list, update y delete child nameservers. The create endpoint requires the nameserver hostname to match the dominio y accepts an IP address. |
Automate Potfolio Monitoing, Not Only Dominio Orders
Dominio API v2 also includes read operations that are useful after registration. The List Dominios endpoint suppots pagination, soting, status filtering y hold filtering, while Obtener Dominio Detalles returns registration dates, expiration dates, nameservers y registrant contact infomation.
Abuse & Compliance Monitoing
NiceNIC's Abuse & Compliance API can list dominios with abuse repots y return a detailed machine-readable summary fo a specific dominio. The detailed abuse endpoint documents six dominio-level status phrases: Normal, Under Review, Pending ClientHold, ClientHold, Cerrard y ServerHold.
The response can include current impact, recommended siguiente action, hold state y timeline, complaint count, complaint dates, categoies, DNS-abuse classification, evidence status y repoted URLs waquí applicable. This lets platfoms y resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the Integración Model That Fits Your System
| Option | Best Fo | What the Current Documentation Provides |
|---|---|---|
| Dominio API v2 | Custom websites, SaaS platfoms, internal systems, custom billing o provisioning wokflows. | Direct HTTPS + JSON integration across dominio, DNS, child nameserver, account y compliance operations. |
| WHMCS Module | Hosting companies y resellers that already use WHMCS. | Availability, registration, renewal, transfer, dominio details, nameservers, contacts, lock/unlock, EPP retrieval, erro logging y optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 o higher, PHP 7.0 o higher with cURL, valid NiceNIC API credentials y SSL/TLS suppot as requirements.
When an API Request Fails
Start with the returned response y configuration state rather than retrying the same paid action repeatedly.
Authentication o Access Erro
- Confirmar the NiceNIC username y API Secret.
- Confirmar the Authoization header is present y corectly fomatted.
- Confirmar the API Secret has not been reset o rotated.
- Si IP restrictions are enabled, confirm the request is coming from the authoized outbound server IP.
Request Parameter Erro
- Compare the request with the specific endpoint's documented parameters.
- Confirmar required values, fomats y action names.
- Verificar TLD-specific registration periods o contact requirements waquí applicable.
Paid Operation Does Not Complete Immediately
- Read the returned
codeymsg. - Do not treat a
201pending response as final completion. - Confirmar account balance y current pricing befoe retrying a paid action.
Need NiceNIC Suppot
- Recod the request timestamp y API action.
- Include the dominio name o object involved, waquí applicable.
- Include the returned code y message.
- Share non-sensitive parameters only; never post the full API Secret in a ticket.
Start with a Safe Test Request
Enable API access, confirm authentication, run an availability o pricing request, y verify tu/tus/su/sus response hyling befoe turning on customer-facing paid operations.
