Confirm hosting readiness
Verify PHP 8.3 or newer is active, ionCube Loader is enabled for that same runtime, and the required extensions and writable paths are ready before upload.
Installation
Install WAPIServer only after your hosting meets the protected runtime requirements
Use this page before you upload the package. It explains the mandatory PHP 8.3 and ionCube requirements, the hosting checks to complete first, the installation flow, and what to verify once the app goes live.
Requirements
Server checklist
PHP 8.3 or newer
ionCube Loader enabled for the same active PHP 8.3+ runtime before opening the installer
MySQL/MariaDB database access
PHP extensions: cURL, PDO MySQL, MySQLi, JSON, OpenSSL, and outbound HTTPS access
Writable directories required by the installer, cache, storage, and logs
Valid license API key from your customer portal
Important
ionCube is mandatory
WAPIServer follows a strict protected deployment model. The installer and core licensing modules rely on ionCube, so your hosting must already have ionCube Loader active before the installer is opened. Shared hosting without ionCube support is not suitable.
The most common installation failure is a missing or incompatible Loader version on the target server. If your hosting panel does not provide ionCube controls, ask the hosting provider to enable ionCube Loader for PHP 8.3 on your account before you start.
Hosting Checklist
Verify these items before upload
PHP 8.3 or higher is selected in your hosting control panel.
ionCube Loader is enabled for that same PHP version.
The host allows outbound HTTPS requests to the licensing server.
Your database credentials are ready and tested.
Required folders are writable before running the installer.
Support Note
What to do on shared hosting
If ionCube is not enabled, first check whether your hosting panel offers an ionCube toggle or PHP extension selector. If it does not, ask your hosting provider to enable ionCube Loader for PHP 8.3 on your account.
If the host cannot provide PHP 8.3 with ionCube support, that hosting environment is not compatible with this WAPI build.
After Launch
What happens after install
WAPIServer validates the license key against the licensing server, receives the active plan payload, verifies the signed payload, and then enables or restricts modules and limits based on that payload.
If the license becomes suspended, expired, invalid, or unauthorized for the domain, the app blocks access with a support-directed message instead of continuing with stale or unsafe state.
Deployment Pattern
Install on a clean subdomain
Use a dedicated subdomain such as wap.example.com, keep the package outside public backup locations, and store database and Super Admin credentials securely after setup.
Before handing the system to operators, verify the dashboard, license status, signed payload sync, and any WhatsApp connectivity required for production use.
Workflow
Download and upload package
Download the installer package from your customer portal, upload it to the target domain or subdomain, and extract it into the application directory.
Create database
Create an empty MySQL or MariaDB database with a dedicated user, then keep the host, database name, username, and password ready for setup.
Run installer and validate license
Open the installer URL, enter the license API key, allow the environment checks to complete, and finish the database and configuration steps.
Create super admin account
Set the first Super Admin account, complete installation, and sign in to the main application dashboard.
Verify live app state
Open Settings, connect WhatsApp if required, and confirm that license status, signed payload sync, and feature access are working correctly.