X
How to Start Using NiceNIC Reseller API v2
NiceNIC Reseller API v2 helps domeen resellers, hosting providers, developers, ja WHMCS users automate domeen operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, v?i custom platfv?im to automate common domeen wv?ikflows such as domeen availability checks, domeen registration, domeen renewal, domeen transfer, nameserver updates, DNS recv?id management, account balance checks, ja transaction review.
Quick Answer
Osta start using NiceNIC J?relmüüja API v2, you need to upgrade sinu NiceNIC account to a reseller tier, configure sinu API settings, create an API passwv?id that is different from sinu account login passwv?id, whitelist the IP-aadress allowed to access the API, ja then connect sinu system to the NiceNIC API v2 endpoint.
Kui you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API wv?ikflow manually.
Who Should Use NiceNIC Reseller API v2?
NiceNIC Reseller API v2 is designed fv?i users who need mv?ie than manual domeen management.
It is suitable fv?i:
What Can You Do with NiceNIC Reseller API v2?
NiceNIC Reseller API v2 can help automate impv?itant parts of the domeen lifecycle.
Depending on sinu account status, API permissions, domeen extension, registry rules, ja available product suppv?it, API functions may include:
Befv?ie You Start
Befv?ie connecting to NiceNIC Reseller API v2, prepare the following:
Step 1: Upgrade Your Account to a J?relmüüja Tier
API access is intended fv?i NiceNIC reseller users. Kui sinu account has not been upgraded yet, log in to sinu NiceNIC account ja review the reseller upgrade options.
A reseller account is useful if you want to:
Ready to automate domeen teenuss?
Uuenda versioonile a NiceNIC reseller account ja connect domeen registration, renewal, transfer, DNS, ja WHMCS wv?ikflows through Reseller API v2.
Step 2: Ava API seadistuss in Your NiceNIC Account
After sinu account is upgraded to a reseller tier, log in to sinu NiceNIC account ja go to the J?relmüüja section.
Then find the API seadistus area. This is wsiin you configure API access fv?i sinu reseller account.
In this area, you should nv?imally complete two key settings:
Step 3: Set a Separate API Parool
Your API passwv?id should be different from sinu NiceNIC account login passwv?id. This matters fv?i both security ja troubleshooting. Kui you use the wrong passwv?id v?i use the account login passwv?id instead of the API passwv?id, authentication may fail.
Recommended practice:
Step 4: Whitelist Your Server IP Aadress
NiceNIC API access requires the IP-aadress that will send API requests. This is usually the public IP-aadress of sinu server, WHMCS installation, billing system, v?i application backend.
Befv?ie saving sinu API settings, confirm the cv?irect outbound IP-aadress with sinu developer v?i hosting provider. Kui the wrong IP-aadress is added, sinu API request may fail even if the username ja API passwv?id are cv?irect.
Common IP-related problems include:
Step 5: Connect to the NiceNIC API v2 Endpoint
After sinu API passwv?id ja IP whitelist are configured, sinu system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests ja returns JSON responses. Your request should include the required authv?iization ja content type headers.
The exact request body depends on the API action you want to perfv?im. Fv?i example, checking domeen availability, registreeriing a domeen, renewing a domeen, updating nameservers, v?i checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building v?i updating sinu integration.
Need the technical documentation?
Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, domeen actions, DNS actions, billing actions, ja WHMCS suppv?it.
Step 6: Test a Safe API Tegevus First
Befv?ie running paid v?i customer-facing actions, test a low-risk API action first.
Recommended first tests:
Your developer should log the following during testing:
Step 7: Connect WHMCS Kui You Use WHMCS Arveldus
Kui sinu business uses WHMCS, you may not need to build every wv?ikflow from zero.
NiceNIC provides WHMCS integration fv?i domeen registrar operations. This can help automate common reseller wv?ikflows such as domeen availability checks, registration, renewal, transfer, ja domeen infv?imation retrieval.
WHMCS integration is especially useful fv?i:
Using WHMCS?
Connect WHMCS with NiceNIC to automate domeen registration, renewal, transfer, ja management wv?ikflows.
Common Setup Problems ja How to Fix Them
1. Authentication Errv?i
An authentication errv?i usually means the API credentials v?i access settings are not cv?irect.
Kontrolli the following:
2. IP Eit K?ikowed v?i Connection Fails
Kui sinu IP-aadress is not allowed, the API request may fail befv?ie the action is processed.
Ask sinu hosting provider v?i server administratv?i to confirm the real outbound IP used fv?i API requests. Then update sinu API settings in sinu NiceNIC account.
3. Invalid Request Fv?imat
Kui the request body, header, v?i parameter fv?imat is incv?irect, the API may return an errv?i response.
Kontrolli:
4. Domeeni registreerimine Failed
A domeen registration request may fail fv?i reasons unrelated to the API connection itself.
Possible causes include:
5. Uuendaal v?i Transfer Failed
Uuendaal ja transfer actions may depend on the domeen extension, domeen status, registry rules, expiration timeline, transfer lock, EPP code, ja account balance.
Fv?i transfer issues, check:
What NiceNIC Can ja Cannot Do
NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, ja suppv?it fv?i domeen operations available through its platfv?im.
However, some domeen actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, v?i third-party systems.
Fv?i example:
Recommended First Integration Wv?ikflow
Kui you are building a new integration, use this sequence:
KKK
1. Do I need a reseller account to use NiceNIC Reseller API v2?
Jah. NiceNIC Reseller API v2 is intended fv?i eligible reseller users. Kui you cannot access API settings, check whether sinu account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login passwv?id as the API passwv?id?
Ei. Fv?i security ja proper configuration, sinu API passwv?id should be different from sinu account login passwv?id.
3. Why does my API request return an authentication errv?i?
Authentication errv?is are commonly caused by the wrong API passwv?id, missing Authv?iization header, incv?irect username, non-whitelisted IP-aadress, v?i a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS?
Jah. NiceNIC provides WHMCS integration fv?i domeen registrar operations such as availability checks, registration, renewal, transfer, ja domeen infv?imation retrieval.
5. Can I registreeri every domeen extension through the API?
Eit always. Domeen registration depends on TLD availability, registry rules, account balance, verification requirements, ja extension-specific restrictions. Some TLDs may require additional documents v?i manual review.
6. What should I test befv?ie going live?
Start with low-risk actions such as account balance lookup, domeen availability check, pricing lookup, ja domeen listing. Do not enable live customer v?iders until authentication, IP whitelist, request fv?imat, response hjaling, ja billing logic are confirmed.
Start Automating Domeen Services with NiceNIC
NiceNIC Reseller API v2 gives resellers, hosting providers, developers, ja WHMCS users a direct way to automate domeen search, registration, renewal, transfer, DNS, ja account wv?ikflows.
NiceNIC Reseller API v2 helps domeen resellers, hosting providers, developers, ja WHMCS users automate domeen operations through a direct API connection.
With the API, eligible NiceNIC resellers can connect their own website, billing system, WHMCS installation, v?i custom platfv?im to automate common domeen wv?ikflows such as domeen availability checks, domeen registration, domeen renewal, domeen transfer, nameserver updates, DNS recv?id management, account balance checks, ja transaction review.
Quick Answer
Osta start using NiceNIC J?relmüüja API v2, you need to upgrade sinu NiceNIC account to a reseller tier, configure sinu API settings, create an API passwv?id that is different from sinu account login passwv?id, whitelist the IP-aadress allowed to access the API, ja then connect sinu system to the NiceNIC API v2 endpoint.
Kui you use WHMCS, you can also connect through the NiceNIC WHMCS integration instead of building every API wv?ikflow manually.
Who Should Use NiceNIC Reseller API v2?
NiceNIC Reseller API v2 is designed fv?i users who need mv?ie than manual domeen management.
It is suitable fv?i:
- Domeen resellers selling domeens to their own customers
- Hostimine providers that want to bundle domeen registration with hosting plans
- Veeb agencies managing many client domeens
- Developers building custom domeen search v?i registration systems
- WHMCS users who want automated domeen operations
- Businesses that need bulk domeen management v?i repeat domeen wv?ikflows
What Can You Do with NiceNIC Reseller API v2?
NiceNIC Reseller API v2 can help automate impv?itant parts of the domeen lifecycle.
Depending on sinu account status, API permissions, domeen extension, registry rules, ja available product suppv?it, API functions may include:
- Kontrolliing domeen availability
- Registreeriing domeen names
- Uuendaing existing domeens
- Transferring domeens with EPP codes
- Listing domeens in sinu account
- Hangiting domeen details
- Updating nameservers
- Updating domeen contact infv?imation
- Kontrolliing domeen pricing
- Managing DNS recv?ids
- Creating ja managing child nameservers
- Kontrolliing account balance
- Reviewing account transactions
- Connecting with WHMCS wv?ikflows
Befv?ie You Start
Befv?ie connecting to NiceNIC Reseller API v2, prepare the following:
- A registreeried NiceNIC account
- An upgraded reseller account v?i eligible reseller access
- Enough account balance fv?i paid domeen operations
- Your API username ja API passwv?id
- The server IP-aadress that will send API requests
- A developer, WHMCS administratv?i, v?i technical team member to complete the integration
- A test wv?ikflow befv?ie using the API fv?i live customer v?iders
Step 1: Upgrade Your Account to a J?relmüüja Tier
API access is intended fv?i NiceNIC reseller users. Kui sinu account has not been upgraded yet, log in to sinu NiceNIC account ja review the reseller upgrade options.
A reseller account is useful if you want to:
- Access reseller-level domeen pricing
- Halda mv?ie domeens under one account
- Use API automation fv?i domeen operations
- Connect WHMCS v?i another billing system
- Build recurring domeen revenue from sinu own customer base
Ready to automate domeen teenuss?
Uuenda versioonile a NiceNIC reseller account ja connect domeen registration, renewal, transfer, DNS, ja WHMCS wv?ikflows through Reseller API v2.
Step 2: Ava API seadistuss in Your NiceNIC Account
After sinu account is upgraded to a reseller tier, log in to sinu NiceNIC account ja go to the J?relmüüja section.
Then find the API seadistus area. This is wsiin you configure API access fv?i sinu reseller account.
In this area, you should nv?imally complete two key settings:
- Set sinu API passwv?id
- Lisa the IP-aadress allowed to access the API
Step 3: Set a Separate API Parool
Your API passwv?id should be different from sinu NiceNIC account login passwv?id. This matters fv?i both security ja troubleshooting. Kui you use the wrong passwv?id v?i use the account login passwv?id instead of the API passwv?id, authentication may fail.
Recommended practice:
- Use a strong API passwv?id
- Do not reuse sinu account login passwv?id
- Stv?ie API credentials securely
- Do not send API credentials through insecure chat v?i public tickets
- Rotate credentials when a developer, vendv?i, v?i fv?imer employee no longer needs access
Step 4: Whitelist Your Server IP Aadress
NiceNIC API access requires the IP-aadress that will send API requests. This is usually the public IP-aadress of sinu server, WHMCS installation, billing system, v?i application backend.
Befv?ie saving sinu API settings, confirm the cv?irect outbound IP-aadress with sinu developer v?i hosting provider. Kui the wrong IP-aadress is added, sinu API request may fail even if the username ja API passwv?id are cv?irect.
Common IP-related problems include:
- The website server IP is different from the outbound API request IP
- WHMCS is hosted behind a firewall, proxy, v?i NAT gateway
- The hosting provider changed the server IP
- Multiple servers are sending API requests but only one IP is whitelisted
- A development server wv?iks, but the production server is not whitelisted
Step 5: Connect to the NiceNIC API v2 Endpoint
After sinu API passwv?id ja IP whitelist are configured, sinu system can send requests to the NiceNIC API v2 endpoint. The API uses HTTP requests ja returns JSON responses. Your request should include the required authv?iization ja content type headers.
The exact request body depends on the API action you want to perfv?im. Fv?i example, checking domeen availability, registreeriing a domeen, renewing a domeen, updating nameservers, v?i checking account balance may require different parameters.
Always follow the latest NiceNIC API v2 documentation when building v?i updating sinu integration.
Need the technical documentation?
Use the official NiceNIC Reseller API v2 documentation to review authentication, response codes, domeen actions, DNS actions, billing actions, ja WHMCS suppv?it.
Step 6: Test a Safe API Tegevus First
Befv?ie running paid v?i customer-facing actions, test a low-risk API action first.
Recommended first tests:
- Kontrolli account balance
- Kontrolli domeen availability
- Hangi domeen pricing
- List domeens
Your developer should log the following during testing:
- Request timestamp
- API action
- Domeen name v?i object used in the test
- Request parameters, excluding sensitive credentials
- Response code
- Response message
- Any errv?i returned by the API
Step 7: Connect WHMCS Kui You Use WHMCS Arveldus
Kui sinu business uses WHMCS, you may not need to build every wv?ikflow from zero.
NiceNIC provides WHMCS integration fv?i domeen registrar operations. This can help automate common reseller wv?ikflows such as domeen availability checks, registration, renewal, transfer, ja domeen infv?imation retrieval.
WHMCS integration is especially useful fv?i:
- Hostimine companies selling domeens with hosting packages
- J?relmüüjas that need automated customer billing
- Agencies managing domeen v?iders fv?i multiple clients
- Businesses that want renewal automation ja customer-facing v?ider wv?ikflows
Using WHMCS?
Connect WHMCS with NiceNIC to automate domeen registration, renewal, transfer, ja management wv?ikflows.
Common Setup Problems ja How to Fix Them
1. Authentication Errv?i
An authentication errv?i usually means the API credentials v?i access settings are not cv?irect.
Kontrolli the following:
- Kinnita that sinu account has reseller access
- Kinnita that you are using the API passwv?id, not sinu account login passwv?id
- Kontrolli whether the API passwv?id was entered cv?irectly
- Kinnita that sinu request includes the Authv?iization header
- Kinnita that sinu server IP-aadress is whitelisted in API settings
- Kontrolli whether sinu request is being sent from a different outbound IP-aadress
2. IP Eit K?ikowed v?i Connection Fails
Kui sinu IP-aadress is not allowed, the API request may fail befv?ie the action is processed.
Ask sinu hosting provider v?i server administratv?i to confirm the real outbound IP used fv?i API requests. Then update sinu API settings in sinu NiceNIC account.
3. Invalid Request Fv?imat
Kui the request body, header, v?i parameter fv?imat is incv?irect, the API may return an errv?i response.
Kontrolli:
- Content-Tüüp is set to application/json
- The request body is valid JSON
- The required parameters are included
- The domeen fv?imat is cv?irect
- The action name matches the API documentation
4. Domeeni registreerimine Failed
A domeen registration request may fail fv?i reasons unrelated to the API connection itself.
Possible causes include:
- The domeen is no longer available
- The TLD has special registration requirements
- The registry requires additional documents
- The account balance is not enough
- The domeen contact infv?imation is incomplete v?i invalid
- The registry rejected the request
5. Uuendaal v?i Transfer Failed
Uuendaal ja transfer actions may depend on the domeen extension, domeen status, registry rules, expiration timeline, transfer lock, EPP code, ja account balance.
Fv?i transfer issues, check:
- The domeen is eligible fv?i transfer
- The domeen is unlocked at the current registrar
- The EPP code is cv?irect
- The domeen is not blocked by registry v?i policy restrictions
- The registrant email v?i transfer approval process has been completed when required
What NiceNIC Can ja Cannot Do
NiceNIC can provide registrar-side API access, reseller account tools, API documentation, WHMCS integration resources, ja suppv?it fv?i domeen operations available through its platfv?im.
However, some domeen actions depend on registry rules, extension policies, verification status, payment status, abuse/compliance status, v?i third-party systems.
Fv?i example:
- Some TLDs may require special documents befv?ie registration
- Some domeens may be locked, expired, under verification, v?i restricted by registry policy
- Some transfer requests may require approval from the losing registrar v?i registrant contact
- DNS changes may take time to propagate globally
- WHMCS behaviv?i may also depend on sinu WHMCS version, module settings, server environment, ja cron configuration
Recommended First Integration Wv?ikflow
Kui you are building a new integration, use this sequence:
- Uuenda versioonile a reseller account
- API seadistamine passwv?id ja IP whitelist
- Connect to the API v2 endpoint
- Test account balance lookup
- Test domeen availability lookup
- Test pricing lookup
- Test nameserver update on a safe internal domeen
- Review response codes ja errv?i hjaling
- Connect WHMCS v?i sinu own billing system
- Enable live registration, renewal, ja transfer wv?ikflows only after testing
KKK
1. Do I need a reseller account to use NiceNIC Reseller API v2?
Jah. NiceNIC Reseller API v2 is intended fv?i eligible reseller users. Kui you cannot access API settings, check whether sinu account has been upgraded to a reseller tier.
2. Can I use my NiceNIC account login passwv?id as the API passwv?id?
Ei. Fv?i security ja proper configuration, sinu API passwv?id should be different from sinu account login passwv?id.
3. Why does my API request return an authentication errv?i?
Authentication errv?is are commonly caused by the wrong API passwv?id, missing Authv?iization header, incv?irect username, non-whitelisted IP-aadress, v?i a request sent from a different outbound server IP.
4. Can I use NiceNIC API v2 with WHMCS?
Jah. NiceNIC provides WHMCS integration fv?i domeen registrar operations such as availability checks, registration, renewal, transfer, ja domeen infv?imation retrieval.
5. Can I registreeri every domeen extension through the API?
Eit always. Domeen registration depends on TLD availability, registry rules, account balance, verification requirements, ja extension-specific restrictions. Some TLDs may require additional documents v?i manual review.
6. What should I test befv?ie going live?
Start with low-risk actions such as account balance lookup, domeen availability check, pricing lookup, ja domeen listing. Do not enable live customer v?iders until authentication, IP whitelist, request fv?imat, response hjaling, ja billing logic are confirmed.
Start Automating Domeen Services with NiceNIC
NiceNIC Reseller API v2 gives resellers, hosting providers, developers, ja WHMCS users a direct way to automate domeen search, registration, renewal, transfer, DNS, ja account wv?ikflows.
Vajad abi? Oleme alati sinu jaoks olemas.
Esita p?ring
- Meie tooted
- Pühendatud server
- Pilveserver
- SSL-sertifikaadid
- ?riemail
- Ettev?tte profiil
- NiceNIC kohta
- Domeeni uudised
- Makseviis
- Lepingud
Autori?igus © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED K?ik ?igused kaitstud