Resellerclub
Sell domain names through your Resellerclub
reseller account.
BAMCS checks availability, registers, transfers and renews domains
automatically, and clients manage their nameservers, contacts, transfer lock,
privacy and EPP codes from the client area.
|
|
| Type |
Domain registrar |
| Version |
1.0.0 |
| API |
Resellerclub HTTP API (httpapi.com) |
Features
Ordering
- Domain search: live availability checks in the storefront. Premium
domains are recognised.
- Register, transfer and renew run automatically once the client's invoice
is paid. Staff can also register a domain straight away from the admin area.
- Expiry date: after registering or renewing, BAMCS reads the real expiry
date from the registry.
- Your balance pays: registrations, transfers and renewals are paid from
your Resellerclub balance. Resellerclub sends no invoice of its own; you bill
your clients in BAMCS as usual.
- Price import: import your Resellerclub prices into Domain Pricing with
a percentage or fixed markup. They are converted into all your store
currencies.
Client self-service
Clients manage their active domains from the client area:
- Nameservers: view and change them.
- Contacts: update the registrant, admin, technical and billing contacts.
- Transfer lock: turn it on or off.
- EPP / auth code: reveal it to transfer the domain away. Every reveal is
logged.
- Child nameservers: create, update and delete them, for example
ns1.theirdomain.com.
- WHOIS privacy: turn it on or off. If you charge for privacy, it is billed
through an invoice.
Automatic sync
- Every day, BAMCS syncs each domain's expiry date, nameservers and transfer
lock from Resellerclub.
- Pending transfers are checked every day and completed automatically once
Resellerclub reports them as active. Failed transfers are flagged.
- Domains that have left your account are marked as transferred away.
- Staff can run a sync for a single domain from its admin page at any time.
Clients and contacts
- Customers: each BAMCS client gets their own customer account in your
Resellerclub account automatically.
- Contacts: WHOIS contacts are created from the contact details entered at
order and reused across that client's domains.
- Fallback: if a client's own customer or contacts can't be created, the
default customer and contact from the settings are used, so the order still
goes through.
Reliability
- Retries: failed registrar actions are retried automatically. If they
still fail, staff and the client are notified, and staff can retry the action
from the domain's admin page.
- Connection check: an hourly check alerts staff if the API stops
responding, for example after an API key change or an IP allowlist problem.
- Credentials: the API key is stored encrypted and is removed from error
messages.
Requirements
- A Resellerclub reseller account with funds in your balance. Orders are
paid from it.
- Your Reseller ID and an API key from the Resellerclub control panel.
- Your BAMCS server's IP address added to the API allowlist in Resellerclub.
- Outbound HTTPS from your server to
httpapi.com. For the demo environment,
that is test.httpapi.com.
- The BAMCS queue worker and scheduler running. Registrations run in the
background, and the daily sync and transfer checks run on the scheduler.
Installation
- In BAMCS, go to Modules → Marketplace and install Resellerclub.
Alternatively, upload the module
.zip under Upload a module package.
- Under Installed Modules, click Activate. This creates the module's
settings. The demo environment is on by default.
- Open Modules → Resellerclub → Settings.
Configuration
Settings
| Setting |
Default |
Description |
| Reseller ID (auth-userid) |
– |
Your Resellerclub reseller ID. |
| API Key |
– |
Your Resellerclub API key. Stored encrypted. |
| Demo environment (test.httpapi.com) |
On |
Sends all requests to Resellerclub's demo system. Turn it off to go live. |
| Customer ID |
– |
Fallback customer used when a client's own customer can't be created. Its prices are also used for the price import. |
| Default Contact ID |
– |
Fallback contact used for all four contact roles when a domain has no contact details. |
| Default Nameserver 1 |
– |
Used for new registrations when neither the client nor the BAMCS-wide default supplies nameservers. |
| Default Nameserver 2 |
– |
As above, for the second nameserver. |
Step 1: API access
- In the Resellerclub control panel, go to Settings → API.
- Copy your Reseller ID and API key.
- Add your BAMCS server's public IP address to the API allowlist.
- Enter the Reseller ID and API key in the module settings.
The demo environment (test.httpapi.com) uses a separate Resellerclub demo
account. Use your demo credentials while Demo environment is on, and your
live credentials once it is off.
Step 2: Fallback customer and contact
In your Resellerclub account, create (or pick) a customer and a contact,
and enter their IDs as Customer ID and Default Contact ID. They are only
used when a client's own details can't be used.
Step 3: Default nameservers
Set Default Nameserver 1 and Default Nameserver 2 if you want
registrations to get your nameservers when nothing else is specified.
Step 4: Assign TLDs
Go to System → Domain Pricing:
- Import: choose Resellerclub, set your markup and import its TLDs and
prices.
- By hand: edit a TLD and pick Resellerclub as its registrar.
Only TLDs assigned to Resellerclub are registered through it.
Step 5: Go live
- With Demo environment on, order a domain end to end and check that it
turns active.
- Enter your live credentials and turn Demo environment off.
Limitations
- No DNS hosting: DNS zone management is not included. Clients point their
nameservers to your DNS servers or to a DNS provider.
- TLDs with extra requirements: TLDs that require extra registrant details or
special contact types can't be registered through the module. Examples
include some country-code TLDs such as .us, .ca, .eu and .uk.
- No redemption restore: domains that have entered redemption can't be
restored from BAMCS. Restore them in the Resellerclub control panel.
- Transfers update daily: a transfer shows as completed on the next daily
check, not instantly.
- Privacy after a transfer: WHOIS privacy isn't switched on automatically
when a transfer completes. The client can turn it on afterwards.
- Phone numbers: phone numbers are sent to the registry correctly when they
are written as
+<country code> <number>, for example +45 12345678.
Numbers without a space after the country code, or without a country code,
may get the wrong country code.
- Price import:
- Prices are treated as USD, so your store needs USD as a currency.
- Check .com after importing. Resellerclub lists it under a different
product key, so the import may skip it.