NiceNIC Reseller API v2 helps domain resellers, hosting providers, developers, and WHMCS users automate domain operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, or custom platform to automate common domain workflows such as domain availability checks, domain registration, domain renewal, domain transfer, nameserver updates, DNS record management, account balance checks, and transaction review.
Quick Answer To start using NiceNIC Reseller API v2, you need to upgrade your NiceNIC account to a reseller tier, configure your API settings, create an API password that is different from your account login password, whitelist the IP address allowed to access the API, and then connect your system to the NiceNIC API v2 endpoint.
If you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API workflow manually.
Who Should Use NiceNIC Reseller API v2? NiceNIC Reseller API v2 is designed for users who need more than manual domain management. It is suitable for:
Domain resellers selling domains to their own customers
Hosting providers that want to bundle domain registration with hosting plans
Web agencies managing many client domains
Developers building custom domain search or registration systems
WHMCS users who want automated domain operations
Businesses that need bulk domain management or repeat domain workflows
If you only register one or two domains occasionally, the NiceNIC control panel may be enough. If you manage many domains or want your own platform to communicate directly with NiceNIC, the Reseller API is the better workflow.
What Can You Do with NiceNIC Reseller API v2? NiceNIC Reseller API v2 can help automate important parts of the domain lifecycle. Depending on your account status, API permissions, domain extension, registry rules, and available product support, API functions may include:
Some actions may depend on registry rules, TLD requirements, domain status, account verification, payment balance, or additional documentation requirements. Always check the API response and the related domain rule before assuming that every extension behaves the same way.
Before You Start Before connecting to NiceNIC Reseller API v2, prepare the following:
A registered NiceNIC account
An upgraded reseller account or eligible reseller access
Enough account balance for paid domain operations
Your API username and API password
The server IP address that will send API requests
A developer, WHMCS administrator, or technical team member to complete the integration
A test workflow before using the API for live customer orders
For better security, do not use your account login password as your API password. Your API password should be separate and used only for API authentication.
Step 1: Upgrade Your Account to a Reseller Tier API access is intended for NiceNIC reseller users. If your account has not been upgraded yet, log in to your NiceNIC account and review the reseller upgrade options. A reseller account is useful if you want to:
Access reseller-level domain pricing
Manage more domains under one account
Use API automation for domain operations
Connect WHMCS or another billing system
Build recurring domain revenue from your own customer base
After your reseller upgrade is completed, you can continue with the API configuration process.
Ready to automate domain services? Upgrade to a NiceNIC reseller account and connect domain registration, renewal, transfer, DNS, and WHMCS workflows through Reseller API v2.
Step 2: Open API Settings in Your NiceNIC Account After your account is upgraded to a reseller tier, log in to your NiceNIC account and go to the Reseller section. Then find the API Setting area. This is where you configure API access for your reseller account. In this area, you should normally complete two key settings:
Set your API password
Add the IP address allowed to access the API
If you cannot see API settings in your account, check whether your reseller upgrade has been completed or contact NiceNIC support for account review.
Step 3: Set a Separate API Password Your API password should be different from your NiceNIC account login password. This matters for both security and troubleshooting. If you use the wrong password or use the account login password instead of the API password, authentication may fail. Recommended practice:
Use a strong API password
Do not reuse your account login password
Store API credentials securely
Do not send API credentials through insecure chat or public tickets
Rotate credentials when a developer, vendor, or former employee no longer needs access
Step 4: Whitelist Your Server IP Address NiceNIC API access requires the IP address that will send API requests. This is usually the public IP address of your server, WHMCS installation, billing system, or application backend.
Before saving your API settings, confirm the correct outbound IP address with your developer or hosting provider. If the wrong IP address is added, your API request may fail even if the username and API password are correct.
Common IP-related problems include:
The website server IP is different from the outbound API request IP
WHMCS is hosted behind a firewall, proxy, or NAT gateway
The hosting provider changed the server IP
Multiple servers are sending API requests but only one IP is whitelisted
A development server works, but the production server is not whitelisted
Step 5: Connect to the NiceNIC API v2 Endpoint After your API password and IP whitelist are configured, your system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests and returns JSON responses. Your request should include the required authorization and content type headers.
The exact request body depends on the API action you want to perform. For example, checking domain availability, registering a domain, renewing a domain, updating nameservers, or checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building or updating your integration.
Need the technical documentation? Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, domain actions, DNS actions, billing actions, and WHMCS support.
Step 6: Test a Safe API Action First Before running paid or customer-facing actions, test a low-risk API action first.
Recommended first tests:
Check account balance
Check domain availability
Get domain pricing
List domains
Avoid starting with live domain registration or transfer until you confirm that authentication, IP whitelist, request format, and response handling are working correctly.
Your developer should log the following during testing:
Step 7: Connect WHMCS If You Use WHMCS Billing If your business uses WHMCS, you may not need to build every workflow from zero.
NiceNIC provides WHMCS integration for domain registrar operations. This can help automate common reseller workflows such as domain availability checks, registration, renewal, transfer, and domain information retrieval.
WHMCS integration is especially useful for:
Hosting companies selling domains with hosting packages
Resellers that need automated customer billing
Agencies managing domain orders for multiple clients
Businesses that want renewal automation and customer-facing order workflows
Before enabling automation in production, test your WHMCS module configuration carefully. Confirm registrar module settings, API credentials, whitelisted IP address, domain pricing, TLD availability, and renewal behavior.
Using WHMCS? Connect WHMCS with NiceNIC to automate domain registration, renewal, transfer, and management workflows.
Common Setup Problems and How to Fix Them 1. Authentication Error An authentication error usually means the API credentials or access settings are not correct. Check the following:
Confirm that your account has reseller access
Confirm that you are using the API password, not your account login password
Check whether the API password was entered correctly
Confirm that your request includes the Authorization header
Confirm that your server IP address is whitelisted in API settings
Check whether your request is being sent from a different outbound IP address
2. IP Not Allowed or Connection Fails If your IP address is not allowed, the API request may fail before the action is processed.
Ask your hosting provider or server administrator to confirm the real outbound IP used for API requests. Then update your API settings in your NiceNIC account.
3. Invalid Request Format If the request body, header, or parameter format is incorrect, the API may return an error response. Check:
Content-Type is set to application/json
The request body is valid JSON
The required parameters are included
The domain format is correct
The action name matches the API documentation
4. Domain Registration Failed A domain registration request may fail for reasons unrelated to the API connection itself. Possible causes include:
The domain is no longer available
The TLD has special registration requirements
The registry requires additional documents
The account balance is not enough
The domain contact information is incomplete or invalid
The registry rejected the request
Review the API response message and check whether the extension has special registry requirements.
5. Renewal or Transfer Failed Renewal and transfer actions may depend on the domain extension, domain status, registry rules, expiration timeline, transfer lock, EPP code, and account balance.
For transfer issues, check:
The domain is eligible for transfer
The domain is unlocked at the current registrar
The EPP code is correct
The domain is not blocked by registry or policy restrictions
The registrant email or transfer approval process has been completed when required
What NiceNIC Can and Cannot Do NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, and support for domain operations available through its platform.
However, some domain actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, or third-party systems.
For example:
Some TLDs may require special documents before registration
Some domains may be locked, expired, under verification, or restricted by registry policy
Some transfer requests may require approval from the losing registrar or registrant contact
DNS changes may take time to propagate globally
WHMCS behavior may also depend on your WHMCS version, module settings, server environment, and cron configuration
For this reason, your integration should always read and store the API response instead of assuming that every action is successful.
Recommended First Integration Workflow If you are building a new integration, use this sequence:
Upgrade to a reseller account
Configure API password and IP whitelist
Connect to the API v2 endpoint
Test account balance lookup
Test domain availability lookup
Test pricing lookup
Test nameserver update on a safe internal domain
Review response codes and error handling
Connect WHMCS or your own billing system
Enable live registration, renewal, and transfer workflows only after testing
FAQ 1. Do I need a reseller account to use NiceNIC Reseller API v2? Yes. NiceNIC Reseller API v2 is intended for eligible reseller users. If you cannot access API settings, check whether your account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login password as the API password? No. For security and proper configuration, your API password should be different from your account login password.
3. Why does my API request return an authentication error? Authentication errors are commonly caused by the wrong API password, missing Authorization header, incorrect username, non-whitelisted IP address, or a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS? Yes. NiceNIC provides WHMCS integration for domain registrar operations such as availability checks, registration, renewal, transfer, and domain information retrieval.
5. Can I register every domain extension through the API? Not always. Domain registration depends on TLD availability, registry rules, account balance, verification requirements, and extension-specific restrictions. Some TLDs may require additional documents or manual review.
6. What should I test before going live? Start with low-risk actions such as account balance lookup, domain availability check, pricing lookup, and domain listing. Do not enable live customer orders until authentication, IP whitelist, request format, response handling, and billing logic are confirmed.
Start Automating Domain Services with NiceNIC NiceNIC Reseller API v2 gives resellers, hosting providers, developers, and WHMCS users a direct way to automate domain search, registration, renewal, transfer, DNS, and account workflows.