NiceNIC Reseller API v2 helps ?????? resellers, hosting providers, developers, ? WHMCS users automate ?????? operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, ?? custom platf??m to automate common ?????? w??kflows such as ?????? availability checks, ?????? registration, ?????? renewal, ?????? transfer, nameserver updates, DNS rec??d management, account balance checks, ? transaction review.
Quick Answer ? start using NiceNIC ????? API v2, you need to upgrade ??? NiceNIC account to a reseller tier, configure ??? API settings, create an API passw??d that is different from ??? account login passw??d, whitelist the ????? IP allowed to access the API, ? then connect ??? system to the NiceNIC API v2 endpoint.
?? you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API w??kflow manually.
Who Should Use NiceNIC Reseller API v2? NiceNIC Reseller API v2 is designed f?? users who need m??e than manual ?????? management. It is suitable f??:
?????? resellers selling ??????s to their own customers
????? providers that want to bundle ?????? registration with hosting plans
??????? agencies managing many client ??????s
Developers building custom ?????? search ?? registration systems
WHMCS users who want automated ?????? operations
Businesses that need bulk ?????? management ?? repeat ?????? w??kflows
?? you only ???? one ?? two ??????s occasionally, the NiceNIC control panel may be enough. ?? you manage many ??????s ?? want ??? own platf??m to communicate directly with NiceNIC, the Reseller API is the better w??kflow.
What Can You Do with NiceNIC Reseller API v2? NiceNIC Reseller API v2 can help automate imp??tant parts of the ?????? lifecycle. Depending on ??? account status, API permissions, ?????? extension, registry rules, ? available product supp??t, API functions may include:
Some actions may depend on registry rules, TLD requirements, ?????? status, account verification, payment balance, ?? additional documentation requirements. Always check the API response ? the related ?????? rule bef??e assuming that every extension behaves the same way.
Bef??e You Start Bef??e connecting to NiceNIC Reseller API v2, prepare the following:
A ????ed NiceNIC account
An upgraded reseller account ?? eligible reseller access
Enough account balance f?? paid ?????? operations
Your API username ? API passw??d
The server ????? IP that will send API requests
A developer, WHMCS administrat??, ?? technical team member to complete the integration
A test w??kflow bef??e using the API f?? live customer ??ders
F?? better security, do not use ??? account login passw??d as ??? API passw??d. Your API passw??d should be separate ? used only f?? API authentication.
Step 1: Upgrade Your Account to a ????? Tier API access is intended f?? NiceNIC reseller users. ?? ??? account has not been upgraded yet, log in to ??? NiceNIC account ? review the reseller upgrade options. A reseller account is useful if you want to:
Access reseller-level ?????? pricing
????? m??e ??????s under one account
Use API automation f?? ?????? operations
Connect WHMCS ?? another billing system
Build recurring ?????? revenue from ??? own customer base
After ??? reseller upgrade is completed, you can continue with the API configuration process.
Ready to automate ?????? ?????s? ???? ?- a NiceNIC reseller account ? connect ?????? registration, renewal, transfer, DNS, ? WHMCS w??kflows through Reseller API v2.
Step 2: ???? ?????? APIs in Your NiceNIC Account After ??? account is upgraded to a reseller tier, log in to ??? NiceNIC account ? go to the ????? section. Then find the ?????? API area. This is w??? you configure API access f?? ??? reseller account. In this area, you should n??mally complete two key settings:
Set ??? API passw??d
???? the ????? IP allowed to access the API
?? you cannot see API settings in ??? account, check whether ??? reseller upgrade has been completed ?? contact NiceNIC supp??t f?? account review.
Step 3: Set a Separate API ????? Your API passw??d should be different from ??? NiceNIC account login passw??d. This matters f?? both security ? troubleshooting. ?? you use the wrong passw??d ?? use the account login passw??d instead of the API passw??d, authentication may fail. Recommended practice:
Use a strong API passw??d
Do not reuse ??? account login passw??d
St??e API credentials securely
Do not send API credentials through insecure chat ?? public tickets
Rotate credentials when a developer, vend??, ?? f??mer employee no longer needs access
Step 4: Whitelist Your Server IP ????? NiceNIC API access requires the ????? IP that will send API requests. This is usually the public ????? IP of ??? server, WHMCS installation, billing system, ?? application backend.
Bef??e saving ??? API settings, confirm the c??rect outbound ????? IP with ??? developer ?? hosting provider. ?? the wrong ????? IP is added, ??? API request may fail even if the username ? API passw??d are c??rect.
Common IP-related problems include:
The website server IP is different from the outbound API request IP
WHMCS is hosted behind a firewall, proxy, ?? NAT gateway
The hosting provider changed the server IP
Multiple servers are sending API requests but only one IP is whitelisted
A development server w??ks, but the production server is not whitelisted
Step 5: Connect to the NiceNIC API v2 Endpoint After ??? API passw??d ? IP whitelist are configured, ??? system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests ? returns JSON responses. Your request should include the required auth??ization ? content type headers.
The exact request body depends on the API action you want to perf??m. F?? example, checking ?????? availability, ????ing a ??????, renewing a ??????, updating nameservers, ?? checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building ?? updating ??? integration.
Need the technical documentation? Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, ?????? actions, DNS actions, billing actions, ? WHMCS supp??t.
Step 6: Test a Safe API ????? First Bef??e running paid ?? customer-facing actions, test a low-risk API action first.
Recommended first tests:
???? account balance
???? ?????? availability
??? ?????? pricing
List ??????s
Avoid starting with live ?????? registration ?? transfer until you confirm that authentication, IP whitelist, request f??mat, ? response h?ling are w??king c??rectly.
Your developer should log the following during testing:
Step 7: Connect WHMCS ?? You Use WHMCS ?????? ?? ??? business uses WHMCS, you may not need to build every w??kflow from zero.
NiceNIC provides WHMCS integration f?? ?????? registrar operations. This can help automate common reseller w??kflows such as ?????? availability checks, registration, renewal, transfer, ? ?????? inf??mation retrieval.
WHMCS integration is especially useful f??:
????? companies selling ??????s with hosting packages
Common Setup Problems ? How to Fix Them 1. Authentication Err?? An authentication err?? usually means the API credentials ?? access settings are not c??rect. ???? the following:
????? that ??? account has reseller access
????? that you are using the API passw??d, not ??? account login passw??d
???? whether the API passw??d was entered c??rectly
????? that ??? request includes the Auth??ization header
????? that ??? server ????? IP is whitelisted in API settings
???? whether ??? request is being sent from a different outbound ????? IP
2. IP ??t ???owed ?? Connection Fails ?? ??? ????? IP is not allowed, the API request may fail bef??e the action is processed.
Ask ??? hosting provider ?? server administrat?? to confirm the real outbound IP used f?? API requests. Then update ??? API settings in ??? NiceNIC account.
3. Invalid Request F??mat ?? the request body, header, ?? parameter f??mat is inc??rect, the API may return an err?? response. ????:
Content-??? is set to application/json
The request body is valid JSON
The required parameters are included
The ?????? f??mat is c??rect
The action name matches the API documentation
4. ????? ?????? Failed A ?????? registration request may fail f?? reasons unrelated to the API connection itself. Possible causes include:
The ?????? is no longer available
The TLD has special registration requirements
The registry requires additional documents
The account balance is not enough
The ?????? contact inf??mation is incomplete ?? invalid
The registry rejected the request
Review the API response message ? check whether the extension has special registry requirements.
5. ?????al ?? Transfer Failed ?????al ? transfer actions may depend on the ?????? extension, ?????? status, registry rules, expiration timeline, transfer lock, EPP code, ? account balance.
F?? transfer issues, check:
The ?????? is eligible f?? transfer
The ?????? is unlocked at the current registrar
The EPP code is c??rect
The ?????? is not blocked by registry ?? policy restrictions
The registrant email ?? transfer approval process has been completed when required
What NiceNIC Can ? Cannot Do NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, ? supp??t f?? ?????? operations available through its platf??m.
However, some ?????? actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, ?? third-party systems.
F?? example:
Some TLDs may require special documents bef??e registration
Some ??????s may be locked, expired, under verification, ?? restricted by registry policy
Some transfer requests may require approval from the losing registrar ?? registrant contact
DNS changes may take time to propagate globally
WHMCS behavi?? may also depend on ??? WHMCS version, module settings, server environment, ? cron configuration
F?? this reason, ??? integration should always read ? st??e the API response instead of assuming that every action is successful.
Recommended First Integration W??kflow ?? you are building a new integration, use this sequence:
???? ?- a reseller account
???? API passw??d ? IP whitelist
Connect to the API v2 endpoint
Test account balance lookup
Test ?????? availability lookup
Test pricing lookup
Test nameserver update on a safe internal ??????
Review response codes ? err?? h?ling
Connect WHMCS ?? ??? own billing system
Enable live registration, renewal, ? transfer w??kflows only after testing
????? ?????? 1. Do I need a reseller account to use NiceNIC Reseller API v2? ??. NiceNIC Reseller API v2 is intended f?? eligible reseller users. ?? you cannot access API settings, check whether ??? account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login passw??d as the API passw??d? ??. F?? security ? proper configuration, ??? API passw??d should be different from ??? account login passw??d.
3. Why does my API request return an authentication err??? Authentication err??s are commonly caused by the wrong API passw??d, missing Auth??ization header, inc??rect username, non-whitelisted ????? IP, ?? a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS? ??. NiceNIC provides WHMCS integration f?? ?????? registrar operations such as availability checks, registration, renewal, transfer, ? ?????? inf??mation retrieval.
5. Can I ???? every ?????? extension through the API? ??t always. ?????? registration depends on TLD availability, registry rules, account balance, verification requirements, ? extension-specific restrictions. Some TLDs may require additional documents ?? manual review.
6. What should I test bef??e going live? Start with low-risk actions such as account balance lookup, ?????? availability check, pricing lookup, ? ?????? listing. Do not enable live customer ??ders until authentication, IP whitelist, request f??mat, response h?ling, ? billing logic are confirmed.
Start Automating ?????? Services with NiceNIC NiceNIC Reseller API v2 gives resellers, hosting providers, developers, ? WHMCS users a direct way to automate ?????? search, registration, renewal, transfer, DNS, ? account w??kflows.