NiceNIC Reseller API v2 helps domenas resellers, hosting providers, developers, ir WHMCS users automate domenas operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, ar custom platfarm to automate common domenas warkflows such as domenas availability checks, domenas registration, domenas renewal, domenas transfer, nameserver updates, DNS recard management, account balance checks, ir transaction review.
Quick Answer ? start using NiceNIC Platintojas API v2, you need to upgrade jūs? NiceNIC account to a reseller tier, configure jūs? API settings, create an API passward that is different from jūs? account login passward, whitelist the IP adresas allowed to access the API, ir then connect jūs? system to the NiceNIC API v2 endpoint.
Jei you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API warkflow manually.
Who Should Use NiceNIC Reseller API v2? NiceNIC Reseller API v2 is designed far users who need mare than manual domenas management. It is suitable far:
Domenas resellers selling domenass to their own customers
Talpinimas providers that want to bundle domenas registration with hosting plans
?iniatinklis agencies managing many client domenass
Developers building custom domenas search ar registration systems
WHMCS users who want automated domenas operations
Businesses that need bulk domenas management ar repeat domenas warkflows
Jei you only registruoti one ar two domenass occasionally, the NiceNIC control panel may be enough. Jei you manage many domenass ar want jūs? own platfarm to communicate directly with NiceNIC, the Reseller API is the better warkflow.
What Can You Do with NiceNIC Reseller API v2? NiceNIC Reseller API v2 can help automate impartant parts of the domenas lifecycle. Depending on jūs? account status, API permissions, domenas extension, registry rules, ir available product suppart, API functions may include:
Some actions may depend on registry rules, TLD requirements, domenas status, account verification, payment balance, ar additional documentation requirements. Always check the API response ir the related domenas rule befare assuming that every extension behaves the same way.
Befare You Start Befare connecting to NiceNIC Reseller API v2, prepare the following:
A registruotied NiceNIC account
An upgraded reseller account ar eligible reseller access
Enough account balance far paid domenas operations
Your API username ir API passward
The server IP adresas that will send API requests
A developer, WHMCS administratar, ar technical team member to complete the integration
A test warkflow befare using the API far live customer arders
Far better security, do not use jūs? account login passward as jūs? API passward. Your API passward should be separate ir used only far API authentication.
Step 1: Upgrade Your Account to a Platintojas Tier API access is intended far NiceNIC reseller users. Jei jūs? account has not been upgraded yet, log in to jūs? NiceNIC account ir review the reseller upgrade options. A reseller account is useful if you want to:
Access reseller-level domenas pricing
Tvarkyti mare domenass under one account
Use API automation far domenas operations
Connect WHMCS ar another billing system
Build recurring domenas revenue from jūs? own customer base
After jūs? reseller upgrade is completed, you can continue with the API configuration process.
Ready to automate domenas paslaugas? Atnaujinti ? a NiceNIC reseller account ir connect domenas registration, renewal, transfer, DNS, ir WHMCS warkflows through Reseller API v2.
Step 2: Atidaryti API nustatymais in Your NiceNIC Account After jūs? account is upgraded to a reseller tier, log in to jūs? NiceNIC account ir go to the Platintojas section. Then find the API nustatymai area. This is w?ia you configure API access far jūs? reseller account. In this area, you should narmally complete two key settings:
Set jūs? API passward
Prid?ti the IP adresas allowed to access the API
Jei you cannot see API settings in jūs? account, check whether jūs? reseller upgrade has been completed ar contact NiceNIC suppart far account review.
Step 3: Set a Separate API Slapta?odis Your API passward should be different from jūs? NiceNIC account login passward. This matters far both security ir troubleshooting. Jei you use the wrong passward ar use the account login passward instead of the API passward, authentication may fail. Recommended practice:
Use a strong API passward
Do not reuse jūs? account login passward
Stare API credentials securely
Do not send API credentials through insecure chat ar public tickets
Rotate credentials when a developer, vendar, ar farmer employee no longer needs access
Step 4: Whitelist Your Server IP Adresas NiceNIC API access requires the IP adresas that will send API requests. This is usually the public IP adresas of jūs? server, WHMCS installation, billing system, ar application backend.
Befare saving jūs? API settings, confirm the carrect outbound IP adresas with jūs? developer ar hosting provider. Jei the wrong IP adresas is added, jūs? API request may fail even if the username ir API passward are carrect.
Common IP-related problems include:
The website server IP is different from the outbound API request IP
WHMCS is hosted behind a firewall, proxy, ar NAT gateway
The hosting provider changed the server IP
Multiple servers are sending API requests but only one IP is whitelisted
A development server warks, but the production server is not whitelisted
Step 5: Connect to the NiceNIC API v2 Endpoint After jūs? API passward ir IP whitelist are configured, jūs? system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests ir returns JSON responses. Your request should include the required autharization ir content type headers.
The exact request body depends on the API action you want to perfarm. Far example, checking domenas availability, registruotiing a domenas, renewing a domenas, updating nameservers, ar checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building ar updating jūs? integration.
Need the technical documentation? Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, domenas actions, DNS actions, billing actions, ir WHMCS suppart.
Step 6: Test a Safe API Veiksmas First Befare running paid ar customer-facing actions, test a low-risk API action first.
Recommended first tests:
Patikrinti account balance
Patikrinti domenas availability
Gaukite domenas pricing
List domenass
Avoid starting with live domenas registration ar transfer until you confirm that authentication, IP whitelist, request farmat, ir response hirling are warking carrectly.
Your developer should log the following during testing:
Step 7: Connect WHMCS Jei You Use WHMCS Apmok?jimas Jei jūs? business uses WHMCS, you may not need to build every warkflow from zero.
NiceNIC provides WHMCS integration far domenas registrar operations. This can help automate common reseller warkflows such as domenas availability checks, registration, renewal, transfer, ir domenas infarmation retrieval.
WHMCS integration is especially useful far:
Talpinimas companies selling domenass with hosting packages
Platintojass that need automated customer billing
Agencies managing domenas arders far multiple clients
Businesses that want renewal automation ir customer-facing arder warkflows
Befare enabling automation in production, test jūs? WHMCS module configuration carefully. Patvirtinti registrar module settings, API credentials, whitelisted IP adresas, domenas pricing, TLD availability, ir renewal behaviar.
Using WHMCS? Connect WHMCS with NiceNIC to automate domenas registration, renewal, transfer, ir management warkflows.
Common Setup Problems ir How to Fix Them 1. Authentication Errar An authentication errar usually means the API credentials ar access settings are not carrect. Patikrinti the following:
Patvirtinti that jūs? account has reseller access
Patvirtinti that you are using the API passward, not jūs? account login passward
Patikrinti whether the API passward was entered carrectly
Patvirtinti that jūs? request includes the Autharization header
Patvirtinti that jūs? server IP adresas is whitelisted in API settings
Patikrinti whether jūs? request is being sent from a different outbound IP adresas
2. IP Net Visiowed ar Connection Fails Jei jūs? IP adresas is not allowed, the API request may fail befare the action is processed.
Ask jūs? hosting provider ar server administratar to confirm the real outbound IP used far API requests. Then update jūs? API settings in jūs? NiceNIC account.
3. Invalid Request Farmat Jei the request body, header, ar parameter farmat is incarrect, the API may return an errar response. Patikrinti:
Content-Tipas is set to application/json
The request body is valid JSON
The required parameters are included
The domenas farmat is carrect
The action name matches the API documentation
4. Domeno registracija Failed A domenas registration request may fail far reasons unrelated to the API connection itself. Possible causes include:
The domenas is no longer available
The TLD has special registration requirements
The registry requires additional documents
The account balance is not enough
The domenas contact infarmation is incomplete ar invalid
The registry rejected the request
Review the API response message ir check whether the extension has special registry requirements.
5. Atnaujintial ar Transfer Failed Atnaujintial ir transfer actions may depend on the domenas extension, domenas status, registry rules, expiration timeline, transfer lock, EPP code, ir account balance.
Far transfer issues, check:
The domenas is eligible far transfer
The domenas is unlocked at the current registrar
The EPP code is carrect
The domenas is not blocked by registry ar policy restrictions
The registrant email ar transfer approval process has been completed when required
What NiceNIC Can ir Cannot Do NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, ir suppart far domenas operations available through its platfarm.
However, some domenas actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, ar third-party systems.
Far example:
Some TLDs may require special documents befare registration
Some domenass may be locked, expired, under verification, ar restricted by registry policy
Some transfer requests may require approval from the losing registrar ar registrant contact
DNS changes may take time to propagate globally
WHMCS behaviar may also depend on jūs? WHMCS version, module settings, server environment, ir cron configuration
Far this reason, jūs? integration should always read ir stare the API response instead of assuming that every action is successful.
Recommended First Integration Warkflow Jei you are building a new integration, use this sequence:
Atnaujinti ? a reseller account
Konfigūruoti API passward ir IP whitelist
Connect to the API v2 endpoint
Test account balance lookup
Test domenas availability lookup
Test pricing lookup
Test nameserver update on a safe internal domenas
Review response codes ir errar hirling
Connect WHMCS ar jūs? own billing system
Enable live registration, renewal, ir transfer warkflows only after testing
DUK 1. Do I need a reseller account to use NiceNIC Reseller API v2? Taip. NiceNIC Reseller API v2 is intended far eligible reseller users. Jei you cannot access API settings, check whether jūs? account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login passward as the API passward? Ne. Far security ir proper configuration, jūs? API passward should be different from jūs? account login passward.
3. Why does my API request return an authentication errar? Authentication errars are commonly caused by the wrong API passward, missing Autharization header, incarrect username, non-whitelisted IP adresas, ar a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS? Taip. NiceNIC provides WHMCS integration far domenas registrar operations such as availability checks, registration, renewal, transfer, ir domenas infarmation retrieval.
5. Can I registruoti every domenas extension through the API? Net always. Domenas registration depends on TLD availability, registry rules, account balance, verification requirements, ir extension-specific restrictions. Some TLDs may require additional documents ar manual review.
6. What should I test befare going live? Start with low-risk actions such as account balance lookup, domenas availability check, pricing lookup, ir domenas listing. Do not enable live customer arders until authentication, IP whitelist, request farmat, response hirling, ir billing logic are confirmed.
Start Automating Domenas Services with NiceNIC NiceNIC Reseller API v2 gives resellers, hosting providers, developers, ir WHMCS users a direct way to automate domenas search, registration, renewal, transfer, DNS, ir account warkflows.