# ApisCP

https://docs.wisecp.com/de/apiscp

Connect ApisCP to WISECP to manage hosting accounts, plans and customer tools from the same service record.

## Accessing the Screen

Open **Products → Servers → Add New Server**; choose **ApisCP** under **Server Automation Module**. Open an existing record from the Servers list.

## Before You Start

You need a working, licensed ApisCP installation and an administrator API key. Prepare the key in ApisCP under **Dev → API Keys**. The PHP environment running WISECP needs the SOAP extension and network access to the panel address and port.

The key needs access to plan and account management. Customer tools also require access to site sessions and their resources. A successful connection test does not establish permission for every operation.

The new form contains connection and capacity settings. Saved servers also have **Preferences**, **Linked Services** and **Import** sections. Selling hosting requires an active server, a hosting product and its pricing currency.

## Connection and Product Settings

- **Address / Hostname**: Both required. Address identifies the panel connection; Hostname names the server. Do not add a URL path. Default ports: 2083 with SSL, 2082 without.
- **Username / API Key**: Username is required by the form; enter the administrator name. API Key is required for authentication. Password cannot replace the key.
- **Verify SSL Certificate**: Enabled for new records. Keep HTTPS and verification enabled. Use Custom Port lets you specify a different connection port.
- **Identity and Capacity**: Monthly Cost starts at zero; select its currency. An empty Maximum Accounts becomes 200. The occupancy alert uses this limit. Nameserver accepts four entries.
- **Plan**: Select an existing ApisCP plan by name under the product's Automation → Module Configuration. The field is optional; choose a plan for defined package limits. Selection fills resource limits.

## Tasks

### Connecting the Server

1. Complete **Connection Information** and click **Test Connection** in the server summary.
2. The test reads the plan list. Check the successful result and complete **Identity and Capacity**.
3. Click **Add New Server** and check the list entry. When editing, use **Save Changes**.

### Mapping a Product and Add-on

1. In the hosting product, choose **ApisCP** under **Automation → Module Assignment**.
2. Under **Server Configuration**, select **Single Server** or **Server Group**. Use matching plan names across group members.
3. Check **Module Configuration → Plan** and **Resource Limits**. Selecting a plan does not import products or prices.
4. Keep the first product hidden and **Automatic Setup** disabled. Click **Save Changes** and check the saved selections.

To sell SSH, use the **Shell (SSH) Access** mapping in the product's **Add-ons** tab. Activation and unsuspension apply SSH access; suspension and cancellation disable it. The module does not create saleable add-ons or order requirements. Provisioning creates the account for the service domain.

### Linking Existing Accounts

1. On the saved server, click **Import → List Results**. The list includes domain, username, plan and email.
2. Select accounts and map each customer, product, billing cycle and dates. Check existing domain links.
3. Click **Import** below the list. In **Linked Services**, verify that the existing account was linked without being recreated.

### Managing the Service

Open the service's **Management → Overview** for account details, disk, bandwidth and resource counts. Creation, suspension, unsuspension, termination, password and plan changes are supported. Operation dialogs are covered in [Service Management](https://docs.wisecp.com/en/service-management).

Changing **Management → Settings → Plan** applies the new plan. Account limits can also be adjusted; restoring package limits removes site overrides. The panel login link opens a session as the site user.

Select tools under the server's **Preferences → Client Area Preferences** and click **Save Changes**. Product and service preferences also limit visibility. Customers open their service's **Management** tab.

Tools: File Manager, FTP Accounts, Databases, Email Accounts, Email Forwarders, Addon Domains, Subdomains, Cron Jobs, PHP Version, SSL Management and Webmail. File operations include navigation, creation, deletion, renaming, permissions, editing, extraction, moving, copying, upload and download.

Manage databases and users through creation/deletion and user password changes. Mailboxes support creation, editing, deletion and quota; FTP supports creation, editing, deletion and directory changes. Forwarders, domains and cron jobs support creation/deletion. PHP versions can change; SSL supports creation/deletion. Separate backup and DNS editing tools are unavailable.

Disk, bandwidth, email, database, subdomain and addon-domain usage can feed metrics. Disk and bandwidth metrics can raise panel caps; disabling them restores plan limits. Periodic collection does not synchronize prices. Review an existing test service's overview and tools before enabling automatic provisioning.

## Things to Watch

> **Data and Quotas**
> 
> Termination deletes the site and its data. Plan changes reset custom limits. Email and FTP accounts share the user quota. SSH grants command-line access; chargeable metrics can incur usage fees.

## Required Permissions

Server settings require **MODULES_SERVERS_SETTINGS**; product editing requires **PRODUCTS_OPERATION**. Service operations also require their respective service permissions.

## Related Articles

- [Adding a Server](https://docs.wisecp.com/en/adding-a-server)
- [Product Automation](https://docs.wisecp.com/en/product-automation)
- [Server Groups](https://docs.wisecp.com/en/managing-server-groups)