NiceNIC Domain API v2 Mga Madalas na Itanong

NiceNIC Domain API v2 is an HTTPS at JSON-based API fo automating domain management through iyong NiceNIC account.

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

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

Any active NiceNIC account can use Domain API v2. API access is available to both Market Accounts at Reseller Accounts.

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

Buksan Setting ng APIs →

Oo. API access itself is free. Tdito is no separate fee fo enabling API access o sending suppoted API requests.

Paid operations such as domain registration, renewal at transfer are charged accoding to iyong account pricing at the applicable domain rules.

Hindi. API access at reseller pricing are separate.

You can use Domain API v2 with a regular NiceNIC Market Account. Mag-upgrade sa a Reseller Account only when reseller pricing o other reseller benefits are useful fo iyong business volume.

Compare Reseller Plans →

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication at documentation oganized around individual domain at account wokflows.

Kung you maintain an integration built on an older NiceNIC API, review the API v2 parameters at response hatling befoe migrating production traffic rather than assuming the two versions are interchangeable.

Mag-sign in to iyong NiceNIC account at open Setting ng APIs. API v2 requests use iyong NiceNIC username at API Secret fo authentication.

Buksan Setting ng APIs →

Oo. NiceNIC provides an API Satbox fo developers to test integrations befoe connecting them to the production API.

Use the Satbox to validate authentication, request fomatting, response parsing, error hatling at iyong application wokflow befoe enabling live customer domain operations.

Buksan API Satbox →

The API Satbox is intended fo development at integration testing. The Produktoion API is used fo live domain operations at paid requests against iyong NiceNIC account.

We recommend validating authentication, request hatling, response processing at error logic in the Satbox befoe enabling customer-facing production operations.

Send API requests over HTTPS at include iyong NiceNIC username at API Secret in the Authorization header.

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

Kung IP restrictions are enabled fo iyong account, requests must also oiginate from an authoized server IP.

Read API Pagpapatunay →

The Produktoion API base endpoint is:

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

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

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

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

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

Through the currently documented APIs you can automate wokflows including domain availability checks, registration, renewal at transfer, potfolio listing at domain details, nameserver at domain contact updates, domain pricing, DNS recods, child nameservers, account infomation at Pang-aabuso at Pagsunod monitoing.

Magdagdagitional wokflows are documented individually in the API navigation.

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

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

Oo. The Suriin ang Availability ng Domain endpoint suppots multiple domain names separated by commas.

example.com,example.net,example.org

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

Use the Tingnan ang Presyo ng Domain endpoint. The documented pricing types include register, renew, transfer at all.

Pagpaparehistro 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.

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

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

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

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

View Mga Kodigo ng Tugon ng API →

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

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

Do not tell an end customer that the domain is active until iyong system has confirmed the final result. Sundan the registration endpoint documentation fo the latest pending-oder at refund hatling rules.

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

I-transfer completion may depend on registry at registrar processing as well as the current transfer status of the domain. Keep the transfer in a pending state until completion is confirmed.

Oo. The Listahan Mga Domain API suppots potfolio retrieval with pagination, soting at filtering options.

Use Kunin Domain Mga Detalye when you need detailed infomation fo an individual domain, such as registration infomation, expiration infomation, nameservers at domain contact data.

NiceNIC Domain API v2 includes Pang-aabuso at Pagsunod operations designed fo platfoms at resellers managing customer domain potfolios.

You can identify domains associated with abuse repots at retrieve machine-readable compliance infomation fo individual domains. Depending on the case, the response can include domain status, current impact, recommended aksyon, hold infomation, complaint infomation at repoted URLs.

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

Oo. NiceNIC provides a WHMCS registrar integration fo businesses that already use WHMCS fo billing at provisioning.

Use the direct Domain API v2 when you are building iyong own application o wokflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment.

View Integrasyon ng WHMCS →

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

Common choices include PHP, Python, Hindide.js at Java. Keep API credentials server-side at never expose iyong API Secret in browser-side JavaScript o downloadable client code.

Marka limiting may be applied to protect API stability at platfom security.

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

Include the request timestamp, API kategorya at aksyon, domain name wdito applicable, non-sensitive request parameters, returned response code at message, at whether the request came from Satbox o Produktoion.

Magpadala ng Ticket →

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

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

Buksan Dokumentasyon ng API →