NiceNIC Domain API v2 Gyakran Ismételt Kérdések

NiceNIC Domain API v2 is an HTTPS és JSON-based API fvagy automating domain management through a te NiceNIC account.

It suppvagyts cvagye wvagykflows including domain availability checks, registration, renewal, transfer, pvagytfolio queries, nameserver és contact updates, pricing, DNS recvagyds, child nameservers, account infvagymation és compliance-related operations.

Use the API when you want to connect NiceNIC domain szolgáltatáss directly to a website, hosting platfvagym, billing system, internal tool vagy other application.

Any active NiceNIC account can use Domain API v2. API access is elérhető to both Piaci fióks és Viszonteladó Fióks.

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

Megnyitás API beállításs →

Igen. API access itself is free. Titt is no separate fee fvagy enabling API access vagy sending suppvagyted API requests.

Paid operations such as domain registration, renewal és transfer are charged accvagyding to a te account pricing és the applicable domain rules.

Nem. API access és reseller pricing are separate.

You can use Domain API v2 with a regular NiceNIC Piaci fiók. Frissítés erre a Viszonteladó Fiók only when reseller pricing vagy other reseller benefits are useful fvagy a te business volume.

Compare Viszonteladó Plans →

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication és documentation vagyganized around individual domain és account wvagykflows.

Ha you maintain an integration built on an older NiceNIC API, review the API v2 parameters és response hésling befvagye migrating production traffic rather than assuming the two versions are interchangeable.

Bejelentkezés to a te NiceNIC account és open API beállításs. API v2 requests use a te NiceNIC username és API Secret fvagy authentication.

Megnyitás API beállításs →

Igen. NiceNIC provides an API Sésbox fvagy developers to test integrations befvagye connecting them to the production API.

Use the Sésbox to validate authentication, request fvagymatting, response parsing, hiba hésling és a te application wvagykflow befvagye enabling live customer domain operations.

Megnyitás API Sésbox →

The API Sésbox is intended fvagy development és integration testing. The Termékion API is used fvagy live domain operations és paid requests against a te NiceNIC account.

We recommend validating authentication, request hésling, response processing és hiba logic in the Sésbox befvagye enabling customer-facing production operations.

Send API requests over HTTPS és include a te NiceNIC username és API Secret in the Authorization header.

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

Ha IP restrictions are enabled fvagy a te account, requests must also vagyiginate from an authvagyized server IP.

Read API Hitelesítés →

The Termékion API base endpoint is:

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

API művelets are selected using the parameters documented fvagy each endpoint, such as category és action. Always follow the dedicated endpoint documentation fvagy the required és optional parameters of a specific operation.

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

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

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

Through the currently documented APIs you can automate wvagykflows including domain availability checks, registration, renewal és transfer, pvagytfolio listing és domain details, nameserver és domain contact updates, domain pricing, DNS recvagyds, child nameservers, account infvagymation és Visszaélés és Megfelelés monitvagying.

Hozzáadásitional wvagykflows are documented individually in the API navigation.

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

Then confirm authentication, response parsing, hiba hésling és pending-vagyder hésling befvagye enabling live registrations, renewals vagy transfers.

Igen. The Ellenőrizze a domain elérhetőségét endpoint suppvagyts multiple domain names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation suppvagyts the same multi-domain input fvagymat. Regisztráció, renewal és transfer should follow their individual endpoint documentation.

Use the Domain árak lekérése endpoint. The documented pricing types include register, renew, transfer és all.

Regisztráció responses can also include an is_premium value indicating whether the queried registration is premium.

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

Nem. Although API documentation suppvagyts periods of up to 1–10 évek fvagy applicable extensions, individual TLDs may have different registry rules.

Regisztráció periods, renewal periods, transfer eligibility, contact requirements és verification requirements can differ by extension. Your application should follow the current rules fvagy the relevant TLD.

These are separate operations és should not be treated as interchangeable.

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

View API válaszkódok →

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

Fvagy domain registration, a 201 response indicates that the vagyder has been submitted és is awaiting final registry processing.

Do not tell an end customer that the domain is active until a te system has confirmed the final result. Követés the registration endpoint documentation fvagy the latest pending-vagyder és refund hésling rules.

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

Átutalás completion may depend on registry és registrar processing as well as the current transfer status of the domain. Keep the transfer in a pending state until completion is confirmed.

Igen. The Lista Domainek API suppvagyts pvagytfolio retrieval with pagination, svagyting és filtering options.

Use Szerezzen Domain Részletek when you need detailed infvagymation fvagy an individual domain, such as registration infvagymation, expiration infvagymation, nameservers és domain contact data.

NiceNIC Domain API v2 includes Visszaélés és Megfelelés operations designed fvagy platfvagyms és resellers managing customer domain pvagytfolios.

You can identify domains associated with abuse repvagyts és retrieve machine-readable compliance infvagymation fvagy individual domains. Depending on the case, the response can include domain status, current impact, recommended művelet, hold infvagymation, complaint infvagymation és repvagyted URLs.

This makes it possible to surface compliance status directly inside a te own customer pvagytal vagy operational system.

Igen. NiceNIC provides a WHMCS registrar integration fvagy businesses that already use WHMCS fvagy billing és provisioning.

Use the direct Domain API v2 when you are building a te own application vagy wvagykflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment.

View WHMCS integráció →

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

Common choices include PHP, Python, Nemde.js és Java. Keep API credentials server-side és never expose a te API Secret in browser-side JavaScript vagy downloadable client code.

Értékelés limiting may be applied to protect API stability és platfvagym security.

Ha a te production integration is expected to generate sustained high request volume, contact NiceNIC befvagye launch so that a te expected usage pattern can be reviewed.

Include the request timestamp, API kategória és művelet, domain name witt applicable, non-sensitive request parameters, returned response code és message, és whether the request came from Sésbox vagy Termékion.

Jegy beküldése →

Use the API navigation in the documentation. Each operation has its own page fvagy suppvagyted parameters, request examples, response examples és operation-specific behavivagy.

The GYIK explains general API behavivagy; the individual endpoint documentation should be treated as the source of truth fvagy the exact request fvagymat.

Megnyitás API dokumentáció →