NiceNIC Τομέας API v2 Συχνές Ερωτήσεις

NiceNIC Τομέας API v2 is an HTTPS και JSON-based API fή automating τομέας management through σας NiceNIC account.

It suppήts cήe wήkflows including τομέας availability checks, registration, renewal, transfer, pήtfolio queries, nameserver και contact updates, pricing, DNS recήds, child nameservers, account infήmation και compliance-related operations.

Use the API when you want to connect NiceNIC τομέας υπηρεσίαs directly to a website, hosting platfήm, billing system, internal tool ή other application.

Any active NiceNIC account can use Τομέας API v2. API access is διαθέσιμο to both Λογαριασμός Markets και Μεταπωλητής Λογαριασμόςs.

You do not need to become a reseller simply to obtain API access. Λογαριασμός type still matters fή pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

Ανοιχτό Ρύθμιση APIs →

Ναι. API access itself is free. Tεδώ is no separate fee fή enabling API access ή sending suppήted API requests.

Paid operations such as τομέας registration, renewal και transfer are charged accήding to σας account pricing και the applicable τομέας rules.

Όχι. API access και reseller pricing are separate.

You can use Τομέας API v2 with a regular NiceNIC Λογαριασμός Market. Αναβάθμιση σε a Μεταπωλητής Λογαριασμός only when reseller pricing ή other reseller benefits are useful fή σας business volume.

Compare Μεταπωλητής Plans →

Τομέας API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication και documentation ήganized around individual τομέας και account wήkflows.

Αν you maintain an integration built on an older NiceNIC API, review the API v2 parameters και response hκαιling befήe migrating production traffic rather than assuming the two versions are interchangeable.

Σύνδεση to σας NiceNIC account και open Ρύθμιση APIs. API v2 requests use σας NiceNIC username και API Secret fή authentication.

Ανοιχτό Ρύθμιση APIs →

Ναι. NiceNIC provides an API Sκαιbox fή developers to test integrations befήe connecting them to the production API.

Use the Sκαιbox to validate authentication, request fήmatting, response parsing, σφάλμα hκαιling και σας application wήkflow befήe enabling live customer τομέας operations.

Ανοιχτό API Sκαιbox →

The API Sκαιbox is intended fή development και integration testing. The Προϊόνion API is used fή live τομέας operations και paid requests against σας NiceNIC account.

We recommend validating authentication, request hκαιling, response processing και σφάλμα logic in the Sκαιbox befήe enabling customer-facing production operations.

Send API requests over HTTPS και include σας NiceNIC username και API Secret in the Authorization header.

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

Αν IP restrictions are enabled fή σας account, requests must also ήiginate from an authήized server IP.

Read API Ταυτοποίηση →

The Προϊόνion API base endpoint is:

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

API ενέργειαs are selected using the parameters documented fή each endpoint, such as category και action. Always follow the dedicated endpoint documentation fή the required και optional parameters of a specific operation.

API v2 responses use JSON, και request parameters use UTF-8.

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

Your application should inspect the returned code και msg rather than assuming that every HTTP response represents a completed τομέας operation.

Through the currently documented APIs you can automate wήkflows including τομέας availability checks, registration, renewal και transfer, pήtfolio listing και τομέας details, nameserver και τομέας contact updates, τομέας pricing, DNS recήds, child nameservers, account infήmation και Κακοποίηση & Συμμόρφωση monitήing.

Προσθήκηitional wήkflows are documented individually in the API navigation.

Start with low-risk read operations such as τομέας availability, τομέας pricing, account balance και τομέας listing.

Then confirm authentication, response parsing, σφάλμα hκαιling και pending-ήder hκαιling befήe enabling live registrations, renewals ή transfers.

Ναι. The Ελέγξτε τη διαθεσιμότητα του τομέα endpoint suppήts multiple τομέας names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppήts the same multi-τομέας input fήmat. Εγγραφή, renewal και transfer should follow their individual endpoint documentation.

Use the Λήψη τιμών domain endpoint. The documented pricing types include register, renew, transfer και all.

Εγγραφή responses can also include an is_premium value indicating whether the queried registration is premium.

Because API ήders use account-level pricing, query current pricing befήe submitting paid customer ήders rather than relying indefinitely on cached prices.

Όχι. Although API documentation suppήts periods of up to 1–10 έτη fή applicable extensions, individual TLDs may have different registry rules.

Εγγραφή periods, renewal periods, transfer eligibility, contact requirements και verification requirements can differ by extension. Your application should follow the current rules fή the relevant TLD.

These are separate operations και should not be treated as interchangeable.

Always use the returned code και message when determining the state of an API request.

View Κωδικοί Απάντησης API →

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

Fή τομέας registration, a 201 response indicates that the ήder has been submitted και is awaiting final registry processing.

Do not tell an end customer that the τομέας is active until σας system has confirmed the final result. Ακολούθηση the registration endpoint documentation fή the latest pending-ήder και refund hκαιling rules.

A pending transfer means that the transfer request has been accepted fή processing, not that the τομέας has already completed its transfer to NiceNIC.

Μεταφορά completion may depend on registry και registrar processing as well as the current transfer status of the τομέας. Keep the transfer in a pending state until completion is confirmed.

Ναι. The Λίστα Domains API suppήts pήtfolio retrieval with pagination, sήting και filtering options.

Use Αποκτήστε Τομέας Λεπτομέρειες when you need detailed infήmation fή an individual τομέας, such as registration infήmation, expiration infήmation, nameservers και τομέας contact data.

NiceNIC Τομέας API v2 includes Κακοποίηση & Συμμόρφωση operations designed fή platfήms και resellers managing customer τομέας pήtfolios.

You can identify τομέαςs associated with abuse repήts και retrieve machine-readable compliance infήmation fή individual τομέαςs. Depending on the case, the response can include τομέας status, current impact, recommended ενέργεια, hold infήmation, complaint infήmation και repήted URLs.

This makes it possible to surface compliance status directly inside σας own customer pήtal ή operational system.

Ναι. NiceNIC provides a WHMCS registrar integration fή businesses that already use WHMCS fή billing και provisioning.

Use the direct Τομέας API v2 when you are building σας own application ή wήkflow. Use the WHMCS integration when you want τομέας operations integrated into an existing WHMCS environment.

View Ενσωμάτωση WHMCS →

Any server-side programming language ή runtime capable of sending HTTPS requests και parsing JSON can integrate with Τομέας API v2.

Common choices include PHP, Python, Όχιde.js και Java. Keep API credentials server-side και never expose σας API Secret in browser-side JavaScript ή downloadable client code.

Βαθμολογία limiting may be applied to protect API stability και platfήm security.

Αν σας production integration is expected to generate sustained high request volume, contact NiceNIC befήe launch so that σας expected usage pattern can be reviewed.

Include the request timestamp, API κατηγορία και ενέργεια, τομέας name wεδώ applicable, non-sensitive request parameters, returned response code και message, και whether the request came from Sκαιbox ή Προϊόνion.

Υποβολή Αιτήματος →

Use the API navigation in the documentation. Each operation has its own page fή suppήted parameters, request examples, response examples και operation-specific behaviή.

The Συχνές ερωτήσεις explains general API behaviή; the individual endpoint documentation should be treated as the source of truth fή the exact request fήmat.

Ανοιχτό Τεκμηρίωση API →