# OpenSRS

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

Connect your OpenSRS reseller account to handle domain orders and manage existing customer domains in WISECP.

## Accessing the Screen

Open **Products → Domains → Domain Name Registrars → All Modules → OpenSRS**: `{admin}/module/registrars?module=OpenSRS`.

## What Is on the Screen

**Module Settings** connects your reseller account. **Import** lists existing domains. This module has no **Import Extensions**, automatic cost update or cost currency controls.

### Preparing the OpenSRS Account

1. Sign in to the OpenSRS Reseller Control Panel as the primary reseller user. Open **Account settings → API settings**.
2. Copy the API key. **Generate new API key** invalidates the previous key, so coordinate replacements with every connected system.
3. For production, open **IP access rules → Edit**. Enter the WISECP server’s outbound IP, select the matching CIDR prefix and **Allow**, then click **Add**.
4. Prepare the separate Horizon test key at [the test control panel](https://manage.test.opensrs.com). See [API key setup](https://support.opensrs.com/support/solutions/articles/201000063475) and [Horizon access](https://support.opensrs.com/support/solutions/articles/201000063061).

The server must reach OpenSRS over HTTPS on port 55443. Production uses rr-n1-tor.opensrs.net; test mode uses horizon.opensrs.net. Horizon requires its API key but does not require IP authorization.

## Settings

- ****Reseller Username****: Required; initially empty. Use the primary reseller username for the selected environment. Sub-users cannot authenticate to the API.
- ****API Key****: Required; initially empty. Enter the selected environment’s API key, not the control panel password.
- ****Test Mode****: Off by default. Changes the endpoint to Horizon. Replace credentials when switching environments; the same fields serve both.
- ****Default Nameservers****: Four initially empty fields. The first two have required markers. Without both, service defaults use system nameservers.

## Tasks

### Connecting and Testing

1. In **Module Settings**, enable **Test Mode** and enter Horizon credentials.
2. Click **Test Connection** beside **Save Changes**. It sends an API ping without registering a domain.
3. After success, click **Save Changes**, then reopen the form to confirm the mode. No separate server record is needed.
4. For production, disable **Test Mode**, enter live credentials, test and save. Fund the reseller balance before purchases.

### Assigning Extensions and Prices

1. Open **Products → Domains → Add Extension**. Enter the extension, prices and supported features, select OpenSRS, then click **Add Extension**.
2. For an existing extension, choose **OpenSRS** under **Registrar** in its row and click **Update Extensions**.
3. Open the row’s **Pricing** window. Enter registration, transfer and renewal prices, then click **Save Changes**.
4. Verify the saved assignment and prices. Update costs manually when OpenSRS changes them; the module does not fetch a price catalog.

### Importing Existing Domains

1. Create the extensions first. Open the module’s **Import** tab, choose customers and check dates against OpenSRS.
2. Click **Import**, then inspect the resulting services under **Orders → Services**. Local service creation does not register or transfer domains.

If the list fails or appears incomplete, compare it with the reseller panel before retrying. A successful ping does not verify account-wide domain listing.

### Domain Orders and Synchronization

Registration sends contacts, the selected period, nameservers and requested privacy. Inbound transfer requires the current registrar’s unlock and authorization code where applicable. Renewal uses the selected years. Synchronization reads dates and transfer results. Check provider status before repeating an uncertain order.

### Managing a Domain

Open a domain under **Orders → Services**. **WHOIS** reads and updates contacts and supports privacy through the active addon. **Transfer → Get Auth (EPP) Code** requests the authorization code.

The displayed transfer-lock control uses OpenSRS’s owner-change lock preference. It does not establish whether the current domain transfer lock is enabled. Check and manage the actual lock in OpenSRS before an outgoing transfer.

**DNS** manages OpenSRS-hosted A, AAAA, CNAME, TXT, MX and SRV records. Each edit replaces the zone. Entered TTL is not sent; custom SRV weight and port cannot be entered through these module methods.

Nameservers are sent with new orders. Later nameserver changes must be made in OpenSRS; editing DNS records does not change domain delegation. This integration has no child nameserver management, DNSSEC, separate forwarding screens or expired-domain recovery. Customer controls depend on permissions and active addons.

## Things to Consider

> **Charges and Zone Replacement**
> 
> Live registrations, transfers, renewals and privacy can charge the reseller balance. Back up DNS before editing and avoid simultaneous changes in both panels.

> **Troubleshooting**
> 
> Check the primary username, correct API key and production IP rules for authentication errors. For timeouts, check outbound TCP 55443. Test registration, transfer, renewal and customer management in Horizon before enabling sales. A successful connection test does not validate these workflows. See [connection troubleshooting](https://support.opensrs.com/support/solutions/articles/201000063062-troubleshooting-api-connections).

## Required Permissions

Setup requires **Domain Name Registrars** permission. Service operations require their corresponding service permissions.

## 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 Records](https://docs.wisecp.com/en/service-whois-records)
- [Service Transfer](https://docs.wisecp.com/en/service-transfer)