# ConnectReseller

https://docs.wisecp.com/fr/connectreseller

Connect your ConnectReseller account to sell domains, import existing services and manage their domain settings through WISECP.

## Accessing the Screen

Open **Products → Domain Names → Domain Registrars → All Modules → ConnectReseller**: `{admin}/module/registrars?module=ConnectReseller`.

## What Is on the Screen?

| Section | Purpose | Effect |
| --- | --- | --- |
| Module Settings | Account, customer and pricing settings | Live connection only |
| Import | Match account domains to customers | Creates WISECP services |
| Import Extensions | Select extensions and profit rate | Updates assignments and prices |

### Prepare the Provider Account

Activate a reseller account. In its panel, open **TOOLS → Profile Settings → API → View API Key**. Add this server's outgoing IP under **whitelist IP addresses**. See the [official API-key guide](https://helpdesk.connectreseller.com/portal/en/kb/articles/how-to-create). Confirm domain and DNS access with the provider. PHP cURL and intl are required; allow HTTPS to api.connectreseller.com. This module uses the ESHOP API and has no sandbox switch or endpoint override.

## Settings

- ****API Key****: Required, initially empty. Enter the reseller API key. Saving encrypts it in the module settings.
- ****Reseller ID****: Optional, initially empty. Account reference only in this module; no balance-query operation uses it.
- ****Default Customer ID****: Initially empty; required for registration and transfer. All new orders use this provider customer, not the WISECP customer ID. Renewal prefers the existing domain's customer.
- ****WHOIS privacy on by default****: Off by default. Requests privacy when the order has no explicit privacy-addon choice; that choice takes priority.
- ****Default Nameserver 1****: Initially empty. Fills missing order nameservers; registration requires at least two.
- ****Default Nameserver 2****: Initially empty. The second address in the fallback pair.
- ****Default Nameservers****: Four additional, initially empty fields; the first two are marked required. Used after the provider-specific fallback pair.
- ****Automatic Cost Update****: Off by default. Updates assigned extension costs daily and sales prices using the profit rate.
- ****Cost Currency****: Default US Dollar (USD). Verify imported currencies; the provider's currency takes priority, with USD when missing.

## Available Actions

### Connect and Check

1. In **Module Settings**, enter the key, confirm the provider customer number and check both nameserver groups.
2. Click **Test Connection**. It requests one account-domain row; an empty account is accepted. Success does not verify funds or the customer number.
3. Click **Save Changes** and reopen the form. No separate WISECP server record is required.

### Import Extensions and Prices

Open **Import Extensions**, select extensions and a profit rate, then click **Import**. Existing assignments and prices may change; new extensions start inactive. The feed supplies one-year registration, renewal and transfer costs, currency and allowed periods. Missing prices do not mean free operations. Check saved costs and sales prices against the provider before enabling sales.

Generic DNS/privacy flags do not confirm extension eligibility or addon entitlement. A premium availability quote does not prove registration support: this module submits registration with premium acceptance disabled. Use the [Domain Extensions guide](https://docs.wisecp.com/en/domain-extensions-and-pricing) to verify mapping, currency and addon prices.

### Import Existing Domains

1. Define the extension, then open **Import**. Search or page through account domains; page sizes are 10, 25, 50 and 100.
2. Select a domain and its existing WISECP customer, then click **Import**. This creates an active annual service without ordering a provider transfer.
3. Open it under **Orders → Services** and check customer, registrar, price, dates and nameservers. Start with one controlled record.

Keep a trial sales extension inactive. Test access and read an existing domain before considering a live order. There is no built-in free test environment.

### Manage a Domain

Registration, incoming transfer, renewal, nameserver changes, WHOIS contacts, lock, privacy and authorization-code retrieval are available. Transfer requires the current code. Restore, DNSSEC and email forwarding are unavailable. Registration sends at most four nameservers; the provider update supports up to 13, while service information returns the first four.

In the service's **WHOIS** section, shared contacts are updated once, with the registrant role first. Other domains using those contacts may change. Child nameservers can be listed, added, renamed, updated and deleted. Renaming and IP changes are separate requests; failure can leave a partial change. Check dependent domains before deleting glue records.

The service's **DNS** section supports A, AAAA, CNAME, MX, NS and TXT. DNS writes require a provider zone identifier and suitable nameservers. Blank TTL becomes 43200 seconds; the minimum is 300. URL forwarding can be read, set, updated and cancelled. It creates an unmasked redirect; the 301/302 choice is not sent and the displayed method is 301.

### Check Status and Customer Access

Compare dates and status with the provider after synchronization. A missing account domain raises an error instead of proving an outgoing transfer. Transfer synchronization reads its progress; rejected requests can report the provider's reason. Verify completion before repeating a request. Customer controls depend on service options, addons and permissions.

## Important Notes

> **Live account and shared customer**
> 
> Registration, transfer, renewal and privacy may incur charges. Confirm the configured provider customer's ownership details before accepting orders for different WISECP customers. Local suspension or cancellation does not delete domains or stop provider billing.

For failures, check the API key, outgoing-IP allowlist, customer number, funds and DNS entitlement. HTTP success alone does not establish provider success. Preserve the response and remove credentials and personal details before sharing it.

## Required Permissions

Configuration requires **Domain Registrars** permission. Domain actions also require appropriate administrator or customer permissions and provider access.

## Related Guides

- [Registrar Configuration](https://docs.wisecp.com/en/registrar-modules)
- [Domain Extensions](https://docs.wisecp.com/en/domain-extensions-and-pricing)
- [Service DNS Management](https://docs.wisecp.com/en/service-dns-management)
- [Service WHOIS Contacts](https://docs.wisecp.com/en/service-whois-records)
- [Service Transfers](https://docs.wisecp.com/en/service-transfer)