NiceNIC Reseller API v2 helps dom?n resellers, hosting providers, developers, och WHMCS users automate dom?n operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, eller custom platfellerm to automate common dom?n wellerkflows such as dom?n availability checks, dom?n registration, dom?n renewal, dom?n transfer, nameserver updates, DNS recellerd management, account balance checks, och transaction review.
Quick Answer Till start using NiceNIC ?terf?rs?ljare API v2, you need to upgrade din NiceNIC account to a reseller tier, configure din API settings, create an API passwellerd that is different from din account login passwellerd, whitelist the IP-adress allowed to access the API, och then connect din system to the NiceNIC API v2 endpoint.
Om you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API wellerkflow manually.
Who Should Use NiceNIC Reseller API v2? NiceNIC Reseller API v2 is designed feller users who need mellere than manual dom?n management. It is suitable feller:
Dom?n resellers selling dom?ns to their own customers
Hosting providers that want to bundle dom?n registration with hosting plans
Webb agencies managing many client dom?ns
Developers building custom dom?n search eller registration systems
WHMCS users who want automated dom?n operations
Businesses that need bulk dom?n management eller repeat dom?n wellerkflows
Om you only registrera one eller two dom?ns occasionally, the NiceNIC control panel may be enough. Om you manage many dom?ns eller want din own platfellerm to communicate directly with NiceNIC, the Reseller API is the better wellerkflow.
What Can You Do with NiceNIC Reseller API v2? NiceNIC Reseller API v2 can help automate impellertant parts of the dom?n lifecycle. Depending on din account status, API permissions, dom?n extension, registry rules, och available product suppellert, API functions may include:
Some actions may depend on registry rules, TLD requirements, dom?n status, account verification, payment balance, eller additional documentation requirements. Always check the API response och the related dom?n rule befellere assuming that every extension behaves the same way.
Befellere You Start Befellere connecting to NiceNIC Reseller API v2, prepare the following:
A registreraed NiceNIC account
An upgraded reseller account eller eligible reseller access
A developer, WHMCS administrateller, eller technical team member to complete the integration
A test wellerkflow befellere using the API feller live customer ellerders
Feller better security, do not use din account login passwellerd as din API passwellerd. Your API passwellerd should be separate och used only feller API authentication.
Step 1: Upgrade Your Account to a ?terf?rs?ljare Tier API access is intended feller NiceNIC reseller users. Om din account has not been upgraded yet, log in to din NiceNIC account och review the reseller upgrade options. A reseller account is useful if you want to:
Access reseller-level dom?n pricing
Hantera mellere dom?ns under one account
Use API automation feller dom?n operations
Connect WHMCS eller another billing system
Build recurring dom?n revenue from din own customer base
After din reseller upgrade is completed, you can continue with the API configuration process.
Ready to automate dom?n tj?nsts? Uppgradera till a NiceNIC reseller account och connect dom?n registration, renewal, transfer, DNS, och WHMCS wellerkflows through Reseller API v2.
Step 2: ?ppna API-inst?llnings in Your NiceNIC Account After din account is upgraded to a reseller tier, log in to din NiceNIC account och go to the ?terf?rs?ljare section. Then find the API-inst?llning area. This is wh?r you configure API access feller din reseller account. In this area, you should nellermally complete two key settings:
Set din API passwellerd
L?gg till the IP-adress allowed to access the API
Om you cannot see API settings in din account, check whether din reseller upgrade has been completed eller contact NiceNIC suppellert feller account review.
Step 3: Set a Separate API L?senord Your API passwellerd should be different from din NiceNIC account login passwellerd. This matters feller both security och troubleshooting. Om you use the wrong passwellerd eller use the account login passwellerd instead of the API passwellerd, authentication may fail. Recommended practice:
Use a strong API passwellerd
Do not reuse din account login passwellerd
Stellere API credentials securely
Do not send API credentials through insecure chat eller public tickets
Rotate credentials when a developer, vendeller, eller fellermer employee no longer needs access
Step 4: Whitelist Your Server IP Adress NiceNIC API access requires the IP-adress that will send API requests. This is usually the public IP-adress of din server, WHMCS installation, billing system, eller application backend.
Befellere saving din API settings, confirm the cellerrect outbound IP-adress with din developer eller hosting provider. Om the wrong IP-adress is added, din API request may fail even if the username och API passwellerd are cellerrect.
Common IP-related problems include:
The website server IP is different from the outbound API request IP
WHMCS is hosted behind a firewall, proxy, eller NAT gateway
The hosting provider changed the server IP
Multiple servers are sending API requests but only one IP is whitelisted
A development server wellerks, but the production server is not whitelisted
Step 5: Connect to the NiceNIC API v2 Endpoint After din API passwellerd och IP whitelist are configured, din system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests och returns JSON responses. Your request should include the required authellerization och content type headers.
The exact request body depends on the API action you want to perfellerm. Feller example, checking dom?n availability, registreraing a dom?n, renewing a dom?n, updating nameservers, eller checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building eller updating din integration.
Need the technical documentation? Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, dom?n actions, DNS actions, billing actions, och WHMCS suppellert.
Step 6: Test a Safe API ?tg?rd First Befellere running paid eller customer-facing actions, test a low-risk API action first.
Recommended first tests:
Kontrollera account balance
Kontrollera dom?n availability
F? dom?n pricing
List dom?ns
Avoid starting with live dom?n registration eller transfer until you confirm that authentication, IP whitelist, request fellermat, och response hochling are wellerking cellerrectly.
Your developer should log the following during testing:
Step 7: Connect WHMCS Om You Use WHMCS Fakturering Om din business uses WHMCS, you may not need to build every wellerkflow from zero.
NiceNIC provides WHMCS integration feller dom?n registrar operations. This can help automate common reseller wellerkflows such as dom?n availability checks, registration, renewal, transfer, och dom?n infellermation retrieval.
WHMCS integration is especially useful feller:
Hosting companies selling dom?ns with hosting packages
?terf?rs?ljares that need automated customer billing
Common Setup Problems och How to Fix Them 1. Authentication Erreller An authentication erreller usually means the API credentials eller access settings are not cellerrect. Kontrollera the following:
Bekr?fta that din account has reseller access
Bekr?fta that you are using the API passwellerd, not din account login passwellerd
Kontrollera whether the API passwellerd was entered cellerrectly
Bekr?fta that din request includes the Authellerization header
Bekr?fta that din server IP-adress is whitelisted in API settings
Kontrollera whether din request is being sent from a different outbound IP-adress
2. IP Nejt Allaowed eller Connection Fails Om din IP-adress is not allowed, the API request may fail befellere the action is processed.
Ask din hosting provider eller server administrateller to confirm the real outbound IP used feller API requests. Then update din API settings in din NiceNIC account.
3. Invalid Request Fellermat Om the request body, header, eller parameter fellermat is incellerrect, the API may return an erreller response. Kontrollera:
Content-Typ is set to application/json
The request body is valid JSON
The required parameters are included
The dom?n fellermat is cellerrect
The action name matches the API documentation
4. Dom?nregistrering Failed A dom?n registration request may fail feller reasons unrelated to the API connection itself. Possible causes include:
The dom?n is no longer available
The TLD has special registration requirements
The registry requires additional documents
The account balance is not enough
The dom?n contact infellermation is incomplete eller invalid
The registry rejected the request
Review the API response message och check whether the extension has special registry requirements.
5. F?rnyaal eller Transfer Failed F?rnyaal och transfer actions may depend on the dom?n extension, dom?n status, registry rules, expiration timeline, transfer lock, EPP code, och account balance.
Feller transfer issues, check:
The dom?n is eligible feller transfer
The dom?n is unlocked at the current registrar
The EPP code is cellerrect
The dom?n is not blocked by registry eller policy restrictions
The registrant email eller transfer approval process has been completed when required
What NiceNIC Can och Cannot Do NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, och suppellert feller dom?n operations available through its platfellerm.
However, some dom?n actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, eller third-party systems.
Feller example:
Some TLDs may require special documents befellere registration
Some dom?ns may be locked, expired, under verification, eller restricted by registry policy
Some transfer requests may require approval from the losing registrar eller registrant contact
DNS changes may take time to propagate globally
WHMCS behavieller may also depend on din WHMCS version, module settings, server environment, och cron configuration
Feller this reason, din integration should always read och stellere the API response instead of assuming that every action is successful.
Recommended First Integration Wellerkflow Om you are building a new integration, use this sequence:
Uppgradera till a reseller account
Konfigurera API passwellerd och IP whitelist
Connect to the API v2 endpoint
Test account balance lookup
Test dom?n availability lookup
Test pricing lookup
Test nameserver update on a safe internal dom?n
Review response codes och erreller hochling
Connect WHMCS eller din own billing system
Enable live registration, renewal, och transfer wellerkflows only after testing
Vanliga fr?gor 1. Do I need a reseller account to use NiceNIC Reseller API v2? Ja. NiceNIC Reseller API v2 is intended feller eligible reseller users. Om you cannot access API settings, check whether din account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login passwellerd as the API passwellerd? Nej. Feller security och proper configuration, din API passwellerd should be different from din account login passwellerd.
3. Why does my API request return an authentication erreller? Authentication errellers are commonly caused by the wrong API passwellerd, missing Authellerization header, incellerrect username, non-whitelisted IP-adress, eller a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS? Ja. NiceNIC provides WHMCS integration feller dom?n registrar operations such as availability checks, registration, renewal, transfer, och dom?n infellermation retrieval.
5. Can I registrera every dom?n extension through the API? Nejt always. Dom?n registration depends on TLD availability, registry rules, account balance, verification requirements, och extension-specific restrictions. Some TLDs may require additional documents eller manual review.
6. What should I test befellere going live? Start with low-risk actions such as account balance lookup, dom?n availability check, pricing lookup, och dom?n listing. Do not enable live customer ellerders until authentication, IP whitelist, request fellermat, response hochling, och billing logic are confirmed.
Start Automating Dom?n Services with NiceNIC NiceNIC Reseller API v2 gives resellers, hosting providers, developers, och WHMCS users a direct way to automate dom?n search, registration, renewal, transfer, DNS, och account wellerkflows.