Reseller Not Found Error Explained: Causes and Fixes
Why Does the Reseller Not Found Error Happen?
The “Reseller Not Found” error means the Reseller ID your automation panel sent doesn't match any account in the DomainNameAPI system. The most common causes are entering your account email address in that field instead of the Reseller ID, a Reseller ID that got corrupted while being copied, or a leftover Reseller ID from an old panel still being used after a migration.
1. Introduction
The “Reseller Not Found” error is often confused with “Invalid API Key,” but it actually points to something different. This error means your Reseller ID is the problem, not your API Key. In other words, the system may have recognized your authentication key just fine — it just couldn't figure out which reseller account it belongs to.
In this guide, we'll walk through what's happening technically, the most common root causes, and exactly how to fix it in WHMCS, WiseCP, HostBill, Blesta, and ClientExec.
2. What This Error Actually Means, Technically

Every request sent to DomainNameAPI carries both a Reseller ID and an API Key together. The Reseller ID is a unique value identifying which reseller account the request is acting on behalf of; the API Key is the authentication credential used to access that account. When the system receives a request, it first tries to match the Reseller ID against an existing account. If no match is found — even if the API Key is perfectly correct — it returns a “Reseller Not Found” error.
Your Reseller ID is shown on the Reseller Settings > Integration Details page, and it's typically a long combination of letters and numbers (sample format: 6e575f24-986d-44b1-851d-324e8967be2b). It should never be confused with your email address, your username, or your account number.
Sample Reseller ID
6e575f24-986d-44b1-851d-324e8967be2b
This is a sample value — your real Reseller ID will be a different combination, shown on your own Integration Details page. The important part: this field expects a value in this format, not your email address or username.
Email or Reseller ID? A Quick Comparison
The table below shows the values most commonly typed into the username field by mistake, and whether they're actually a Reseller ID:
3. The Most Common Causes and How to Fix Them
1) An Email Address Entered in the Reseller ID Field
This is, by far, the most common cause. Some users fill the module's “Username” field with the email address they use to log into their panel — but DomainNameAPI expects a Reseller ID in that field, not an email address.
Fix: Copy your real Reseller ID from the Integration Details page and enter it in the module's username field; remove your email address from that field entirely.
DomainNameAPI Technical Team's Observation
A significant share of the “Reseller Not Found” tickets our support team receives trace back to an email address being entered in the Reseller ID field. In these cases, the error doesn't go away even when the API Key is completely correct, because the system checks for a Reseller ID match first.
2) A Stray Character Introduced While Copying the Reseller ID
Copying the Reseller ID from the panel and pasting it into the module can introduce an extra space or an invisible character before or after the value. The result looks identical on screen but is invalid to the system.
Fix: Copy the Reseller ID again directly from the panel and paste it straight into the field; confirm there's no leading or trailing space after pasting. If you're unsure, type the value in manually instead.
3) An Old Reseller ID Left Over After Migration
If your account has been migrated to the new DomainNameAPI platform, any Reseller ID left over from the old panel (cp.domainnameapi.com) is no longer valid. If your module is still configured with that old value, the system won't recognize the request.
Fix: Update your module settings with the current Reseller ID that was emailed to you once migration completed. If you can't find that email, you can resend it from the Integration Details page using the “Email Me My Details” button.
4) Reseller ID and API Key Fields Swapped
Entering the Reseller ID in the password field and the API Key in the username field — essentially swapping the two — can also trigger this error, because the system tries to interpret whatever's in the username field as the Reseller ID.
Fix: Double-check the mapping: Username = Reseller ID, Password = API Key.
5) Using the Reseller ID From the Wrong Sub-Reseller Account
If you manage multiple sub-reseller accounts, each one has its own distinct Reseller ID. Using your main account's Reseller ID in a sub-reseller's module configuration (or vice versa) will trigger this error.
Fix: Make sure you're pulling the Reseller ID from the specific sub-reseller panel you're trying to configure.
6) An Outdated or Unpatched Module Version
An old module version may send the Reseller ID to the API in the wrong format or under the wrong parameter name, which the system then fails to recognize.
Fix: Download the latest module file for your panel from the official GitHub repository, overwrite your existing files, and re-save your Reseller ID and API Key.
4. How This Differs from Other Authentication Errors
Knowing which field is likely at fault is the fastest way to diagnose this error correctly:
| Error Message | Field Usually at Fault | Quick Fix |
|---|---|---|
| Reseller Not Found | Reseller ID is wrong, missing, or swapped | Re-enter the correct Reseller ID |
| Invalid API Key | API Key is wrong, missing, or outdated | Re-enter the correct API Key |
| Authentication Failed | Both fields are wrong or not set at all | Re-enter both fields from scratch |
| Unauthorized / Access Denied | Still connecting with an old username/password pair | Reconfigure using Reseller ID + API Key |
5. Decision Flow: If You're Getting a Reseller Not Found Error
Work Through These Checks in Order
1. Is the value in the username field your Reseller ID, or your email address?
— Email address → Replace it with the real Reseller ID from your Integration Details page.
— Reseller ID → Move to step 2.
2. Could a space or stray character have been introduced while copying the Reseller ID?
— Yes → Re-type the value manually.
— No → Move to step 3.
3. Have you recently gone through an account migration?
— Yes → The Reseller ID from your old panel is no longer valid; use the current one from the new platform.
— No → Move to step 4.
4. Do you manage more than one sub-reseller account?
— Yes → Confirm you're using the Reseller ID that belongs to the correct sub-reseller account.
— No → Check your module version and your API Key.
6. Fix the Reseller Not Found Error in 5 Minutes

Work through this checklist before opening a support ticket — it resolves most cases on its own:
- Is the username field actually populated with your Reseller ID?
- Double-check: is the value you entered an email address?
- Is there a leading or trailing space in the value you copied?
- Are you using the current Reseller ID issued after migration?
- Are you using the correct ID for the sub-reseller account you're trying to configure?
- Is the module you're using on the latest version?
7. The Correct Field, Panel by Panel
The table below shows exactly where the Reseller ID belongs in each panel:
8. Panel-by-Panel Guide and Module Download Links
If your module is outdated, download the current version first and re-save your Reseller ID and API Key afterward.
WHMCS Reseller Not Found Error
In WHMCS, this error is usually caused by an incorrect value in the Username field under System Settings > Domain Registrars > DomainNameAPI. You can download the current module here:
WiseCP Reseller Not Found Error
In WiseCP, the error can originate from the Reseller Credentials fields under Products/Services > Domain Registration > Setup/Settings. You can download the current module here:
HostBill Reseller Not Found Error
In HostBill, check the Username field under Settings > Modules > Domain Registrars > DomainNameAPI. You can download the current module here:
Blesta Reseller Not Found Error
In Blesta, re-enter the Reseller ID for the relevant account row under Settings > Company > Modules > Domain Name API > Manage. You can download the current module here:
ClientExec Reseller Not Found Error
In ClientExec, check whether the username field under Settings > Plugins > Registrars > DomainNameAPI contains an email address or an outdated value.
9. When Should You Open a Support Ticket?
If the error persists after going through every check above, it's likely something specific to your account, and our support team will need to take a look.
- Reseller ID is correct and entered in the correct field
- API Key is correct and entered in the correct field
- Your current server IP is whitelisted under Integration Details
- Module is on the current version
- You're using the correct sub-reseller account
If you've checked all five and the error is still there, go ahead and open a support ticket — attaching your module's log output will help our team resolve it faster.
10. Frequently Asked Questions
What's the difference between a Reseller ID and an API Key?
Your Reseller ID is a unique identifier for which reseller account a request is acting on behalf of, and it goes in the module's username field. Your API Key is the authentication credential for that account, and it goes in the password field. Both are sent together with every request.
Where can I find my Reseller ID?
In your reseller panel, go to My Account > Reseller Settings > Integration Details to view your Reseller ID. You can also have it re-sent to your registered email using the “Email Me My Details” button.
Is my Reseller ID the same as my email address?
No. Your Reseller ID is a completely separate value from your email address — typically a long combination of letters and numbers. It's shown separately on the Integration Details page.
Why am I still getting a Reseller Not Found error when my API Key is correct?
Because this error isn't about your API Key at all; the system checks for a Reseller ID match first. If your Reseller ID is wrong, missing, or in the wrong field, the error persists regardless of how correct your API Key is.
Can I still use my old Reseller ID after a migration?
No. If your account has been migrated to the new platform, the Reseller ID from your old panel is no longer valid. You need to use the current Reseller ID issued to you after migration.
I manage multiple sub-reseller accounts — which Reseller ID should I use?
Each sub-reseller account has its own unique Reseller ID. You need to pull the Reseller ID for the specific account you're configuring from that sub-reseller's own panel; your main account's Reseller ID won't work for sub-reseller operations.
Which field should the Reseller ID go in?
In most panels, the Reseller ID goes in the “Username” field, and the API Key goes in the “Password” field. Field labels vary slightly between panels, but the logic is the same.
Can my Reseller ID change?
Your Reseller ID is a fixed value tied to your account and doesn't normally change. A platform migration is the one exception — in that case, a new Reseller ID is issued and the old one becomes invalid.
Is Reseller Not Found the same as Unauthorized?
No, they point to different things. Unauthorized usually relates to an API Key or IP-authorization issue, while Reseller Not Found specifically means the Reseller ID didn't match anything in the system. They're resolved through different checks.
Does updating the module change my Reseller ID?
No. Updating module files only changes the connection layer between your panel and the API; your Reseller ID, API Key, and domains are unaffected.
I accidentally shared my Reseller ID with someone else — what should I do?
A Reseller ID alone can't grant access to your account (the API Key is also required), but as a precaution, it's a good idea to contact our support team and have them review your account.
How do I confirm my Reseller ID is entered correctly?
Go into your module settings and run a balance check or connection test. If it succeeds, your Reseller ID and API Key are both working correctly together.
11. Conclusion
The “Reseller Not Found” error is often mistaken for “Invalid API Key,” but it points to a different root cause: look at your Reseller ID, not your API Key. The most common triggers are an email address typed into that field, a copy-paste error, or a leftover value from before a migration. Working through the order in this guide usually resolves it within a few minutes.
If the issue persists, reviewing your module's log output or reaching out to our support team will get you unblocked quickly.
With DomainNameAPI, you can sell domains in 200+ countries and get your WHMCS, WiseCP, HostBill, Blesta, or ClientExec integration running in minutes.
