Reseller Club API
This page explains the Reseller Club API integration in GoAdmio. It connects GoAdmio to your ResellerClub account so the panel can automatically change a domain's nameservers to Cloudflare — completing the automation chain that adds all DNS records to Cloudflare without manual steps.
Location: Admin Panel → Domain API → Reseller Club API
Overview
GoAdmio's DNS automation has two halves:
- Cloudflare — hosts the DNS zone and creates all records (A, AAAA, MX, SPF, DKIM, DMARC, autodiscover, autoconfig)
- The registrar — must point the domain's nameservers at Cloudflare so Cloudflare becomes authoritative
Without the Reseller Club API, the customer must manually change nameservers in the ResellerClub control panel — a step that is easy to forget and causes hours of "why isn't my site live?" tickets.
> Note: The Reseller Club API is one of several registrar integrations in GoAdmio. See Spaceship API and Dynadot API for other registrars. All of them require the Cloudflare API to be configured first — Cloudflare is where the DNS records live.
How the Automation Works
When you run /go/dns domain.com on a domain registered through ResellerClub, GoAdmio:
- Creates the zone in Cloudflare — via the Cloudflare API
- Adds all DNS records — A, AAAA, MX, SPF, DKIM, DMARC, autodiscover, autoconfig
- Reads the Cloudflare nameservers assigned to the zone
- Updates the nameservers at ResellerClub — via the Reseller Club API
- Verifies the change (if supported)
> Warning: Nameserver changes at the registrar can take minutes to 48 hours to propagate worldwide, depending on the TLD and the old TTL. The automation removes the manual step, but it does not speed up propagation.
What the Page Shows
| Field | Description |
|---|---|
| Reseller ID | Your ResellerClub reseller ID (the account number) |
| API Key | Your ResellerClub API key |
| API Username (if required) | The API username configured in ResellerClub |
| Sandbox Mode (if available) | Whether to use ResellerClub's test environment |
| Save / Verify | Apply and test the credentials |
| Status | Whether the credentials are valid |
> Note: The exact fields depend on ResellerClub's API authentication model and your GoAdmio version. ResellerClub uses a Reseller ID and an API key configured in the ResellerClub control panel.
Prerequisites
Before configuring the Reseller Club API:
- A ResellerClub account — https://www.resellerclub.com (or a regional ResellerClub site)
- The domains registered through ResellerClub — you must control the domain at ResellerClub to change its nameservers
- Your Reseller ID — the numeric account ID shown in the ResellerClub control panel
- An API key — generated in the ResellerClub control panel
- The Cloudflare API configured — required; Cloudflare hosts the DNS
- The nameservers Cloudflare assigns — GoAdmio reads these automatically
- Root access to the GoAdmio Admin Panel
How to Get Your ResellerClub Credentials
Step 1 — Log in to ResellerClub
- Go to your ResellerClub control panel (the URL depends on your region — e.g., https://www.resellerclub.com for global, or a regional site).
- Log in with your reseller account.
Step 2 — Find your Reseller ID
- Navigate to Settings → Personal Information (or Account).
- Copy your Reseller ID — a numeric value.
Step 3 — Generate an API key
- Navigate to Settings → API (or Tools → API).
- Click Create API Key (or the equivalent in your interface).
- Copy the API key — it is shown only once.
- If required, also set an API username (some ResellerClub configurations use a dedicated API user).
Step 4 — Whitelist your server IP (if required)
Some ResellerClub API configurations require you to authorize the IP address that will call the API.
- Add your GoAdmio server's public IPv4 to the IP allowlist in ResellerClub.
- Add the IPv6 address if you use IPv6.
- Save.
How to Configure the Integration
- Log in to the GoAdmio Admin Panel.
- Navigate to Domain API → Reseller Club API.
- Paste your Reseller ID.
- Paste the API Key.
- If required, enter the API Username.
- Click Save (or Verify).
> Tip: If verification fails, check the error message — it usually indicates an invalid key, a missing IP allowlist entry, or insufficient API permissions.
Using the Integration
Once configured, the integration is used automatically when you run DNS provisioning commands:
Add a single domain
```bash
/go/dns domain.com