Skip to main content
From the public Git repository at bitbucket.org/mailchannels/mailchannels-email-api-whmcs-plugin. Clone it and copy the two module directories into WHMCS, or build a release ZIP first. See Install the WHMCS plugin.
Yes. The plugin is free and MIT-licensed, but it manages sub-accounts under your own MailChannels Email API parent account. You are billed by MailChannels for your parent account according to your MailChannels plan. Your customers are billed by you, through WHMCS, at prices you set.
No. The plan builder shows illustrative examples only. Prices in WHMCS are your store prices. The plugin never reads or changes MailChannels billing.
MailChannels blocks sending from that sub-account until the next MailChannels billing period. Other customers are unaffected. The customer sees their usage against the limit in the client area.
MailChannels blocks sending from every sub-account until the next billing period, even those with remaining individual capacity. The Shared parent ceiling card on the addon page shows parent usage. See Capacity and reconciliation.
Yes. Sub-account limits do not reserve parent capacity, so you can over-allocate based on expected usage. The addon warns you when allocations exceed the parent limit so you can make that decision deliberately.
No. The plugin makes no remote change on renewal. MailChannels controls billing-period resets for the parent account and all sub-accounts. A customer’s WHMCS billing date and their MailChannels usage period are independent.
Sub-accounts have access to the MailChannels Console and API with their own credentials, so a customer can create additional keys there. The plugin manages only the credentials it created. It never revokes or reconciles customer-created credentials.
Credentials are never sent by email. The plan builder disables the welcome email so a template cannot accidentally include them. You can enable a welcome email on the product afterwards as long as it does not reference credential fields. Customers retrieve credentials from the client area.
Handles are derived from your installation and the WHMCS service ID and cannot be changed. The company name is set once at creation from the client’s WHMCS company name. You can change it in the MailChannels Console; the plugin does not overwrite it.
No. Messages submitted over SMTP do not produce MailChannels delivery webhooks and are not DKIM-signed by MailChannels. Customers who need either should use an API plan. See Email API vs SMTP.
Only the sub-account handle, the client’s company name (or a generic label), the send limit, and, for customer-initiated domain checks, the domain name entered. See Security and data flow.
No. The provisioning module declares that it does not require a server. Leave the product’s server group empty.
The plugin is tested against WHMCS 9.0 and 8.13 LTS with PHP 8.2 and 8.3. Other versions are not supported.
No. WHMCS Marketplace listings are reviewed for completeness only. WHMCS does not audit, certify, or test third-party module code.
Open a request with MailChannels support and include the plugin version and the details listed in Troubleshooting.