SMSAPI in Hummerce is an integration with the SMSAPI SMS gateway service - once configured, the store gains SMS as an extra alert channel, alongside email and admin panel notifications. This lets selected store events (e.g. an order confirmation, a login code) send a text message instead of, or alongside, an email.
Last updated: 2026-09-29.
¶ Benefits and use cases
- SMS as an alert channel - any alert configured in the store (see Email templates and alerts) can send an SMS message instead of, or alongside, an email, when the recipient has a phone number.
- Delivery report - SMSAPI returns to the store whether a message was delivered, sent, or returned an error.
- A sender name matching the store's brand - once verified in SMSAPI, messages go out under the store's name instead of the default "SMSAPI".
- A history of sent messages in the admin panel, for review and diagnostics.
- The store connects to the SMSAPI gateway over HTTP or HTTPS (configurable), authenticating with the SMSAPI account's login and password.
- The message is sent with the configured sender field (Sender name) - without a configured sender, the message goes out as "SMSAPI".
- SMS is one of the notification types in the store's general alert mechanism - it appears as an option in the alert template only when the SMSAPI module is configured, see Email templates and alerts.
- SMSAPI sends feedback about the status of each message (sent, delivered, error) to a callback address configured in the SMSAPI account - the address is provided during implementation.
- The delivery status is saved with the sent message and is visible on the list of sent SMS messages in the panel.
- The integration is part of the Hummerce platform - it works in all current store versions.
- An SMSAPI account (login, password, a verified sender name).
- The alerts through which SMS actually gets sent - see Email templates and alerts.
- The recipient's phone number saved on the customer account or in the order.
- Requires implementation - the integration doesn't turn on by itself. Scope: setting up an SMSAPI account, verifying the sender name, configuring the module in the store panel (login, password, sender, protocol), setting the callback address in the SMSAPI account, choosing which alerts should send SMS, and testing sending and delivery.
- Minimum estimated time: module configuration and connecting it to one alert - from 3 h.
- The time for a specific implementation depends on the number of alerts that should send SMS and the scope of testing - we quote it individually.
- SMS only sends as part of an alert, to a single recipient of the event (e.g. the customer placing the order) - the panel has no separate screen for writing and sending an SMS to a chosen group of customers.
- Sending requires a sender name verified in SMSAPI - without it, messages go out as "SMSAPI".
- We do not verify the configuration for legal compliance (e.g. the customer's consent to SMS contact) - the legal basis is set by the store.
- Sending SMS to a chosen group of customers directly from the panel, without tying it to a specific alert.
Does SMSAPI work as a separate channel, or does it need to be tied to the store's alerts?
SMS is sent through the alert mechanism - the SMSAPI module supplies the SMS gateway itself, and the choice of which events should send SMS is set in the alert template.
Does the store know whether the SMS reached the recipient?
Yes. SMSAPI sends back a delivery report, visible on the list of sent SMS messages in the panel.
Can an SMS be sent to a group of customers at once from the panel?
There's no separate screen for that - SMS is sent through an alert, to the recipient of a specific event.
How long does implementing the SMSAPI integration take?
Basic configuration and connecting it to one alert - from 3 h. The scope depends on the number of alerts that should send SMS.
Is the SMS sender name the store's name?
It can be, once verified in the SMSAPI account (the Settings -> Sender fields tab). Without verification, messages go out as "SMSAPI".
Want to check how SMS notifications could work in your store? Contact the Hummerce team (in Polish).
- Module configuration (the SMSAPI configuration group): SMSAPI username and password, sender name, sending over HTTPS, gateway address lists (HTTP and HTTPS).
- List of sent SMS messages - a history of messages sent from the store to SMSAPI, with delivery status.
- Configuration on the SMSAPI side: the Settings -> API tab (the callback address for delivery reports) and Settings -> Sender fields (sender name verification).
¶ REST API and MCP
- No dedicated REST API operations or MCP tools for SMSAPI - the module's configuration is changed through the general configuration tools.
- MCP (AI assistant - MCP server):
ec2_config_search, ec2_config_get, ec2_config_set, ec2_modules_list also work on this module; the SMSAPI password, as a secret, is neither read nor written by the assistant - it's changed in the panel.
The SMS message content comes from the template assigned to the alert - see Email templates and alerts, the section on variables inserted into the content.
The module doesn't add its own item or customer parameters - it uses the phone number saved with the customer or the order.