Matt Steady

<p>Share a link once, then change where it points — without resending anything.</p>
<p>Swirv is a personal link manager for WordPress. Every link lives on your own domain (such as <code>yoursite.com/swirv/download</code>), and its destination is yours to change at any time. Send a link to 200 people today, swap its target tomorrow, and all 200 land in the new place — no third-party shortener, no resending, and never that “sorry, use this link instead” message.</p>
<h4>Passes: a private link for every recipient</h4>
<p>A <strong>Pass</strong> is a personalised version of a link — its own unguessable URL and a reference label (a supporter, a customer, a newsletter). Issue everyone their own Pass and they all inherit the parent link’s target. Change the link once and every Pass follows. Emailed a track download to your supporters, then need to make a tweak? Edit the target once, and every one of them now gets the fix.</p>
<h4>What you can do</h4>
<ul>
<li>Redirect links on your own domain, e.g. <code>yoursite.com/swirv/download</code></li>
<li>Re-point any link after it has been shared — no dead links, no resending</li>
<li>Issue personalised Passes under any link, each with its own private URL</li>
<li>Group links into Campaigns, with optional public campaign pages</li>
<li>Track clicks with daily analytics charts — privacy-first, no visitor IPs stored</li>
<li>Generate QR codes for any link or campaign</li>
<li>Run Health Scans to catch dead, redirecting, or slow target URLs</li>
<li>Import and export everything as JSON/ZIP for backups and migrations</li>
<li>Optional prefixless links (<code>yoursite.com/download</code>), with clash-checking against existing pages</li>
</ul>
<p>A companion plugin, <strong>Swirv Pro</strong>, adds advanced Pass controls — access limits, expiry, self-destruct — and more, for larger libraries and tighter workflows.</p>
<h4>Privacy-first by design</h4>
<p>Swirv keeps your link and click data on your own site. It never stores visitor IP addresses — a click records only a 2-letter country code — and Swirv URLs are served <code>noindex, nofollow</code> with a <code>no-referrer</code> policy. Detailed click tracking is optional and can be switched off entirely under <strong>Swirv <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Data</strong>. Full disclosure of the minimal, opt-in external services Swirv can use is in the <strong>External services</strong> section below.</p>
<h3>External services</h3>
<p>Swirv stores a 2-letter ISO country code per click, for visitor-country analytics. It derives that code from Cloudflare’s <code>CF-IPCountry</code> request header when present, or otherwise by looking the visitor’s IP up against a local MaxMind GeoLite2-Country database if one has been installed. The raw IP is read only to derive the country code and is never written to the database in any form, hashed or otherwise. With neither source available, the country code is stored empty.</p>
<h4>Requests to your target URLs</h4>
<p>Swirv makes server-side HTTP requests to the target URLs you have added, in three situations: (1) when you save a Link, Swirv sends a HEAD request to learn the target’s MIME type, used to drive per-link image-target download behaviour; (2) Health scans send HEAD requests when you run them; (3) when a visitor clicks an image-typed Link that has the force-download behaviour active, Swirv fetches the image body server-side and streams it back to the visitor. In all three cases the destination server receives a request from your WordPress site. The save-time HEAD probe sends a User-Agent of <code>Swirv Target Probe/{version} (+{your_site_url}; content-type sniffer)</code>; the Health-scan and inline-download paths use the default WordPress HTTP API User-Agent. No visitor data, click data, or WordPress account information is sent in the body of these requests.</p>
<h4>Cloudflare</h4>
<p>Swirv reads Cloudflare’s HTTP_CF_IPCOUNTRY request header when your site is fronted by Cloudflare. Swirv does not send any data to Cloudflare; the header is set by Cloudflare’s edge on incoming requests as part of your site’s existing Cloudflare relationship. The only data Swirv extracts is the 2-letter ISO country code, used for visitor-country analytics on this install. If your site is not on Cloudflare, this code path is inert.</p>
<p>Service: Cloudflare (https://www.cloudflare.com)<br />
Terms of service: https://www.cloudflare.com/terms/<br />
Privacy policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>MaxMind GeoLite2</h4>
<p>Swirv can connect to MaxMind, Inc. to download the GeoLite2-Country database, used to map visitor IP addresses to a 2-letter country code for analytics. The database is stored locally on your server under <code>wp-content/uploads/swirv/geoip/</code> and every country lookup happens on your server against that local copy; Swirv never sends visitor IP addresses to MaxMind.</p>
<p>Swirv contacts MaxMind only after a site administrator has added their own MaxMind licence key under <strong>Swirv <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Analytics <span aria-hidden="true" class="wp-exclude-emoji">→</span> Geography</strong> and either (a) clicked the <strong>Download / update database now</strong> button, or (b) the monthly refresh cron has fired since the key was saved. Without a saved licence key, the cron fires but takes no action and Swirv makes no outbound request to MaxMind.</p>
<p>The licence key you enter is stored on your own server in the WordPress options table (as the <code>swirv_maxmind_license_key</code> option), in the same plain-text form WordPress core uses for other site credentials and API keys; Swirv applies no separate encryption to it. It is never transmitted anywhere except to MaxMind as the <code>license_key</code> parameter of the download request described below. Anyone with read access to your WordPress database (including other plugins running on the site) can read it, so treat your MaxMind key like any other site secret. You can clear it at any time by emptying the field and saving.</p>
<p>When downloading the database, Swirv issues a single HTTPS GET request to <code>https://download.maxmind.com/app/geoip_download</code> with three query-string parameters: <code>edition_id=GeoLite2-Country</code>, <code>license_key={your key}</code>, and <code>suffix=tar.gz</code>. The request uses the default WordPress HTTP API User-Agent (which includes your site URL, per WordPress core). No visitor data, click data, or WordPress account information is sent by Swirv as part of this download request.</p>
<p>Service: MaxMind GeoLite country database (https://www.maxmind.com)<br />
Terms of use: https://www.maxmind.com/en/terms-of-use<br />
Privacy policy: https://www.maxmind.com/en/privacy-policy<br />
GeoLite end-user licence agreement: https://www.maxmind.com/en/geolite/eula</p>
<h4>swirv.org</h4>
<p>Swirv links the admin to swirv.org (the Swirv project’s marketing and documentation site, operated by Matt Steady) in three places:</p>
<ul>
<li>The <strong>About <span aria-hidden="true" class="wp-exclude-emoji">↗</span></strong> submenu item under Swirv in the WordPress admin sidebar opens https://swirv.org in a new tab. This is the Swirv project’s home page — project information, contact details, and links to documentation.</li>
<li>The <strong>Swirv Pro <span aria-hidden="true" class="wp-exclude-emoji">↗</span></strong> submenu item — visible only when the Swirv Pro companion plugin is not active — opens https://swirv.org/swirvfree/upgrade.html in a new tab. This is the page describing the Swirv Pro companion plugin.</li>
<li>The <strong>★ Swirv Pro</strong> badges next to Pro-only features in the admin (the Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Analytics tab, the Passes and Analytics admin pages, and the Health Scan page) also open https://swirv.org/swirvfree/upgrade.html in a new tab.</li>
</ul>
<p>These are user-initiated browser links, not server-side calls. Swirv does not send any visitor data, click data, site URL, or WordPress account information to swirv.org as part of these links — the connection happens in the user’s browser when they click the link. Standard web-server access logs on swirv.org (the visitor’s IP address, user-agent, referer) apply the same as any browser navigation to any site.</p>
<p>Service: swirv.org (the Swirv project’s marketing and documentation site)<br />
Terms of use: https://swirv.org/terms.html<br />
Privacy policy: https://swirv.org/privacy</p>
<h4>A note on uptime-monitor names</h4>
<p>Swirv ships a default “exclude monitor traffic” list (Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Analytics) containing names such as Pulsetic, UptimeRobot, Better Stack, Hyperping, StatusCake, and Pingdom. These are not external services Swirv connects to. They are text substrings Swirv matches against the User-Agent header of incoming requests to your own site, so that clicks from those uptime monitors are not counted in your analytics. No data is sent to any of these services, and no network connection is made.</p>
<h3>Source Code and Bundled Libraries</h3>
<p>Swirv ships two minified third-party JavaScript libraries and keeps all custom Swirv JavaScript readable and unminified.</p>
<ul>
<li><code>admin/js/chart.umd.min.js</code> is Chart.js 4.5.1. Readable source is available at <code>https://www.npmjs.com/package/chart.js/v/4.5.1</code> and <code>https://github.com/chartjs/Chart.js/tree/v4.5.1</code>.</li>
<li><code>admin/js/qrcode.min.js</code> is node-qrcode 1.5.4, bundled from the browser entry point as an IIFE that exposes <code>window.QRCode</code>. Readable source is available at <code>https://www.npmjs.com/package/qrcode/v/1.5.4</code> and <code>https://github.com/soldair/node-qrcode/tree/v1.5.4</code>.</li>
</ul>


Swirv

Share a link once, change where it points later — no resending. Personalised Passes give each recipient their own private URL.

onlinecity

<p>Send SMS notifications for WooCommerce orders, create SMS campaigns, manage contacts, and add two-factor authentication – powered by GatewayAPI.com.</p>
<h3>📝 Description</h3>
<p>GatewayAPI for WordPress is a powerful SMS plugin that combines WooCommerce transactional SMS notifications with a high-performance campaign and contact management system.</p>
<p>The plugin allows you to automatically send SMS messages when WooCommerce orders change status, as well as create and send personalized SMS campaigns to large contact lists.</p>
<p>You can also add an extra layer of security to your WordPress site with SMS-based two-factor authentication, helping protect your login process with verification codes sent directly to your mobile device.</p>
<p>Version 2 is a complete rewrite of the plugin, with a strong focus on performance, reliability, and modern WordPress standards.</p>
<p>All SMS messages are delivered via GatewayAPI.com, one of Europe’s leading SMS gateways.</p>
<h3>⭐ Main Features</h3>
<h4>🛒 WooCommerce SMS Notifications</h4>
<ul>
<li>Send automatic SMS messages based on WooCommerce order status changes</li>
<li>Separate message templates for customer and internal recipients</li>
<li>Fully configurable per order status</li>
<li>Supports all standard WooCommerce order statuses</li>
</ul>
<h4>🔐 Two-Factor Authentication</h4>
<ul>
<li>Add an extra layer of security to your WordPress login</li>
<li>SMS-based verification codes sent automatically during login</li>
<li>Can be limited to specific roles and phone countries</li>
<li>Works with standard WordPress authentication</li>
<li>Uses GatewayAPI’s reliable SMS delivery</li>
</ul>
<h4>📢 SMS Campaigns & Broadcasts</h4>
<ul>
<li>Send SMS campaigns to large contact lists</li>
<li>High throughput and stable delivery using Action Scheduler</li>
<li>Designed to work reliably even on shared web hosting</li>
<li>Background processing</li>
</ul>
<h4>📇 Contact & List Management</h4>
<ul>
<li>Manage contacts directly in WordPress</li>
<li>Import and export contacts using CSV files</li>
<li>Store custom fields per contact</li>
<li>Reusable contact lists for campaigns</li>
<li>Use contact fields for mail-merged SMS content</li>
</ul>
<h4>✉️ Personalized Message Templates</h4>
<ul>
<li>Mail-merge support for campaigns and WooCommerce messages</li>
<li>Use dynamic placeholders such as customer data, order data, and custom fields</li>
<li>Supports both GSM and Unicode SMS</li>
<li>Configurable sender ID per message</li>
</ul>
<h4>🧩 Frontend Shortcodes</h4>
<ul>
<li>Signup: Allow users to subscribe to your SMS lists directly from your website.</li>
<li>Update Profile: Enable users to update their contact details and group subscriptions.</li>
<li>Unsubscribe: Provide a simple way for users to opt-out of SMS communications.</li>
<li>Send SMS: Enable SMS sending from the frontend (e.g. for internal tools).</li>
</ul>
<h4>🚀 Built for Reliability & Scale</h4>
<ul>
<li>Uses Action Scheduler (the same job system used by WooCommerce)</li>
<li>Non-blocking background processing</li>
<li>Suitable for very large campaigns (100,000+ recipients)</li>
<li>No PHP timeouts or long-running requests</li>
</ul>
<h3>⚠️ Coming from v1.x? Some features are gone</h3>
<p>The following features are not part of this plugin anymore:</p>
<ul>
<li>Receiving or processing incoming SMS messages</li>
<li>Contact Form 7-integration</li>
</ul>
<p>These features had very low usage and were removed to simplify the plugin. If you need this, consider the legacy version of the plugin (any version before 2.0).</p>
<h3>🌍 About GatewayAPI.com</h3>
<ul>
<li>Founded in 1999</li>
<li>One of Europe’s leading SMS providers</li>
<li>Offices in Copenhagen, Odense, and Aalborg, Denmark</li>
<li>Hundreds of millions of SMS messages delivered yearly</li>
<li>No subscriptions – pay only for what you send</li>
<li>Fast and reliable SMS delivery worldwide</li>
</ul>
<h3>🔧 Installation</h3>
<ol>
<li>Create a free account at https://gatewayapi.com/</li>
<li>Install and activate the plugin</li>
<li>Go to GatewayAPI <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings</li>
<li>Add your API Token from your GatewayAPI.com account</li>
<li>Play around! Send a test campaign or setup a WooCommerce Order hook</li>
</ol>
<h3>🚀 Getting Started</h3>
<h4>🛍️ WooCommerce Notifications</h4>
<p>After installation, you can enable SMS notifications per WooCommerce order status.<br />
Each status can send messages to customers, internal recipients, or both.</p>
<p>Place a test order to confirm everything is working as expected.</p>
<h4>📨 Campaign Messaging</h4>
<p>You can create SMS campaigns without WooCommerce:</p>
<ul>
<li>Import contacts via CSV or add them manually</li>
<li>Organize contacts into lists</li>
<li>Create a personalized SMS campaign</li>
</ul>
<h4>🔐 Two-Factor Authentication</h4>
<p>To add SMS-based two-factor authentication to your WordPress site:</p>
<ul>
<li>Go to GatewayAPI <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Two-Factor</li>
<li>Enable two-factor authentication</li>
<li>Configure which user roles should use two-factor authentication</li>
<li>Optionally limit to specific phone countries for security</li>
<li>Set a grace period if needed</li>
</ul>
<h3>🧩 Shortcodes</h3>
<p>The plugin provides shortcodes to integrate SMS features into your frontend.</p>
<h4>📝 Common Attributes</h4>
<ul>
<li>action: (required) One of signup, update, unsubscribe, send_sms.</li>
<li>recaptcha: Set to 1 to enable Google reCAPTCHA (must be configured in settings).</li>
<li>embed_css: Set to 1 to embed basic styling for the form.</li>
<li>groups: Comma-separated list of group/tag IDs to target.</li>
<li>allowed_countries: Comma-separated list of country codes (e.g., 45,44).</li>
</ul>
<h4>➕ Signup Form</h4>
<p>[gatewayapi action=”signup” groups=”1,2,3″]</p>
<h4>🔄 Update Profile</h4>
<p>[gatewayapi action=”update”]</p>
<h4>❌ Unsubscribe</h4>
<p>[gatewayapi action=”unsubscribe”]</p>
<h4>✉️ Send SMS</h4>
<p>[gatewayapi action=”send_sms” groups=”1″]</p>
<p>Security Warning: The send_sms action allows sending SMS messages from your frontend. This can be dangerous if left open to the public as it could be abused to send spam or drain your GatewayAPI credits.</p>
<p>We strongly recommend combining this with a security system, such as:<br />
* Placing the shortcode on a password-protected page.<br />
* Restricting access to specific user roles using a membership plugin.<br />
* Always enabling recaptcha=”1″ to prevent automated abuse.</p>
<h3>❓ Frequently Asked Questions</h3>
<h4>Can this plugin handle very large SMS campaigns?</h4>
<p>Yes. Campaigns are processed using Action Scheduler, ensuring stable delivery, high throughput, and retries — even on shared hosting environments.</p>
<h4>Does this plugin support personalized SMS messages?</h4>
<p>Yes. You can use dynamic placeholders from contacts and WooCommerce orders to send fully personalized, mail-merged SMS messages.</p>
<h4>Is WooCommerce required?</h4>
<p>WooCommerce is only required for order-based SMS notifications.<br />
Campaign messaging and contact management work without WooCommerce.</p>
<h3>🔗 External services</h3>
<p>This plugin connects to the GatewayAPI.com service to send SMS messages. This external service is required for the plugin’s primary functionality, which is delivering transactional and campaign SMS messages.</p>
<p>When sending an SMS, the plugin transmits the recipient phone number, message content, and related metadata (such as sender ID) to GatewayAPI.com. For WooCommerce notifications, order-related data may be used to generate the message content before it is sent.</p>
<p>No data is sent to GatewayAPI.com unless an SMS is actively being sent by the site administrator or triggered by configured WooCommerce events.</p>
<p>This service is provided by GatewayAPI ApS.</p>
<p>Privacy policy, terms and conditions, data processing agreement, and security certifications (including ISAE 3000 and ISAE 3402) are available at:<br />
https://gatewayapi.com/security-and-compliance/</p>
<h3>📋 Changelog</h3>
<h4>2.1.4</h4>
<ul>
<li>Improved UI for tag dropdowns when there are many items.</li>
</ul>
<h4>2.1.3</h4>
<ul>
<li>New bulk actions for all contacts matching current filters: Delete/deactivate/activate contact + add/remove tag.</li>
<li>Contacts list UI update, more sleek import/export buttons.</li>
</ul>
<h4>2.1.2</h4>
<ul>
<li>Improved contact import: Papa Parse CSV parser with auto-delimiter detection and auto-created meta fields from unknown columns.</li>
<li>Fallback support: Support for our previous (<v2.0) CSV format support.</li>
</ul>
<p><h4>2.1.1</h4>
</p>
<ul>
<li>Bugfix: The recipient tags were not properly sent to the campaign creation UI.</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>New feature: Shortcodes for signup, updating contact details, and unsubscription.</li>
<li>New feature: Shortcode for sending SMS from the frontend (use with caution and combine with security-system).</li>
<li>Bugfix: Contacts filtering by tag didn’t work.</li>
</ul>
<h4>2.0.8</h4>
<ul>
<li>The migration tool should now be available to all users of the 1.x-versions, as some were missing it.</li>
</ul>
<h4>2.0.7</h4>
<ul>
<li>Tool for easy and automatic migration of old contacts, contact fields and contact groups included.</li>
<li>Automatically migrates and uses old OAuth key.</li>
</ul>
<h4>2.0.5</h4>
<ul>
<li>Bugfix: For users upgrading from 1.x, a missing capability upgrade made the plugin unavailable until deactivate + reactivate.</li>
</ul>
<h4>2.0.4</h4>
<ul>
<li>Two-factor authentication has been re-added to the plugin.</li>
</ul>
<h4>2.0.2-2.0.3</h4>
<ul>
<li>No changes. These versions exist because we have been working on automating release processes.</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>Minor modifications to ensure best-practices as per WordPress guidelines.</li>
</ul>
<h4>2.0.0</h4>
<ul>
<li>Complete rewrite of the plugin!</li>
</ul>
<h4>1.8.3</h4>
<ul>
<li>Compability up to WordPress 6.3.1.</li>
</ul>
<h4>1.8.2</h4>
<ul>
<li>Bugfix: Built in shortcode defaulted to the posts title as the name of the new recipient. Now defaults to ”, as expected.</li>
</ul>
<h4>1.8.1</h4>
<ul>
<li>Bugfix: Built in shortcode for signup did not work properly, when allowing the user to select groups.</li>
</ul>
<h4>1.8.0</h4>
<ul>
<li>Support for using our GatewayAPI.eu-setup!</li>
<li>Bugfix: 2FA login security could fail on PHP 7.4+.</li>
</ul>
<h4>1.7.6</h4>
<ul>
<li>Bugfix: Fixing that GatewayAPI Shortcode for signup had stopped saving some meta-fields since 1.7.2.</li>
</ul>
<h4>1.7.5</h4>
<ul>
<li>Bugfix: Default country code did not apply correctly in the country drop downs.</li>
</ul>
<h4>1.7.4</h4>
<p>Compability with Contact Form 7.</p>
<ul>
<li>Bugfix: Signup via Contact Form 7 works again (upgraded to being compatible with CF7’s newer window.fetch based approach of AJAX).</li>
<li>Bugfix: Notices in CF7-integration (PHP) and a typo, causing an exception in frontend JS on CF7-forms.</li>
</ul>
<h4>1.7.3</h4>
<p>Bugfix release.</p>
<ul>
<li>Bugfix: Saving recipient details using the UI and via Excel-importer, works properly again.</li>
<li>Bugfix: SMS Reply-feature works again.</li>
</ul>
<h4>1.7.2</h4>
<p>This release strengthens the overall security, thanks to input from an external security audit.</p>
<p>We highly recommend upgrading to this version, as it hardens the security of our plugin, especially on WordPress-installation with multiple users<br />
which may have users of lower roles than editor.</p>
<ul>
<li>Consistent use of nonce’s in AJAX requests, to prevent CSRF and prevent privilege escalation.</li>
<li>Enforce correct roles for various actions, preventing potential privilege escalation.</li>
<li>Improved sanitizing, validation and escaping of input and output.</li>
<li>All PHP-files are now secured from direct access.</li>
<li>Refactored function prefixes from <code>gwapi_</code>, <code>_gwapi_</code> and <code>_gatewayapi_</code> to <code>gatewayapi_</code> only.</li>
</ul>
<h4>1.7.1</h4>
<ul>
<li>Bugfix: Notifications were not sent.</li>
</ul>
<h4>1.7.0</h4>
<ul>
<li>New: Notification module: Receive SMS-notifications when various actions occur in WordPress
<ul>
<li>BETA: Please get in touch if you have ideas/suggestions for improving this feature.</li>
</ul>
</li>
<li>New: Default country code field setting (previously all country selectors defaulted to +45/Denmark).</li>
<li>New: Programmer actions <code>gwapi_form_subscribe</code> and <code>gwapi_form_unsubscribe</code> added. The first is triggered when new recipients complete signup via<br />
our shortcode-forms and the latter on unsubscription via the shortcode-forms.</li>
<li>Optimization: Removed various unneeded dependencies.</li>
<li>Danish translation updated, including the notification-module.</li>
<li>Readme updated to inform about notification-module and other text improvements.</li>
</ul>
<h4>1.6.9</h4>
<ul>
<li>New! Create Notifications to automatically notify recipients by SMS when a WP action is executed.</li>
</ul>
<h4>1.6.8</h4>
<ul>
<li>Bugfix: Prefix wasn’t specified for all instances of db_table usages.</li>
</ul>
<h4>1.6.7</h4>
<ul>
<li>Bugfix: Previously imported recipients was prevented from being re-imported if they had been deleted.</li>
</ul>
<h4>1.6.6</h4>
<ul>
<li>Bugfix: While using recipients import, group recipients was not counted correctly after the import was completed.</li>
</ul>
<h4>1.6.5</h4>
<ul>
<li>Improved: Import of recipients optimized.</li>
</ul>
<h4>1.6.4</h4>
<ul>
<li>Compatible with WordPress 5.5</li>
<li>Improved: Integration with Contact Form 7 now supports shortcode for mandatory fields</li>
<li>Tweak: Updated UI and descriptions.</li>
</ul>
<h4>1.6.3</h4>
<ul>
<li>Compatible with WordPress 5.4</li>
<li>New! Recipient groups can now default to unchecked when using short-code</li>
<li>Tweak: Minor updates to UI.</li>
</ul>
<h4>1.6.2</h4>
<ul>
<li>Tweak: The frontend forms now use regular SMS instead of Display SMS for two-factor, as requested by multiple users.</li>
<li>Bugfix: When using tags, the list of tags sent to GatewayAPI could end in a situation, with the same tag-data repeated.</li>
</ul>
<h4>1.6.1</h4>
<ul>
<li>Removed URL in two-factor SMS as it was unnecessary and caused SMS’es to be blocked by GatewayAPI’s new link-scanner.</li>
</ul>
<h4>1.6.0</h4>
<ul>
<li>New! Custom encoding for SMS’es, allowing SMS’es with emojis and other special characters.
<ul>
<li>UI which detects what encoding should be used, always recommending the cheapest option (ie. most characters per SMS).</li>
<li>API-method <code>gwapi_send_sms</code> has new argument for setting encoding.</li>
<li>Fully backwards-compatible, defaulting to standard-encoding.</li>
</ul>
</li>
<li>Compatible with WordPress 5.1</li>
</ul>
<h4>1.5.2</h4>
<ul>
<li>Compable with WordPress 5.0.3.</li>
<li>Fix: Excel-export of recipients did not work unless “SMS Inbox” was enabled.</li>
<li>Fix: Notices in Excel-export.</li>
</ul>
<h4>1.5.1</h4>
<ul>
<li>Updated Danish translations (primarily the two-factor settings and frontend).</li>
<li>Fix: Our shortcode had unintentionally been renamed. We now support both <code>[gwapi]</code> and <code>[gatewayapi]</code>.</li>
<li>Fix: Two-factor-module caused fatal error on PHP 5. Also fixed general notices in two-factor module.</li>
<li>Fix: Two-factor module caused fatal error when creating new WordPress-users.</li>
</ul>
<h4>1.5.0</h4>
<ul>
<li>New! Two-factor security upgrade to your WordPress! (optional)</li>
<li>New! Blacklisting of phone numbers.</li>
<li>Improved: Searching recipients by phone number works.</li>
<li>Improved: Better support for 10.000+ recipients + a progress bar for showing progress.</li>
</ul>
<h4>1.4.2</h4>
<ul>
<li>Recipients:
<ul>
<li>Added option to blacklist phone numbers.</li>
<li>Added support for searching recipients list by phone number (previously only by name).</li>
<li>Added drop down on recipients list, for filtering by group.</li>
</ul>
</li>
<li>Fix: Improved handling of huge lists of recipients (ie. 1.000+ recipients in one SMS)</li>
</ul>
<h4>1.4.1</h4>
<ul>
<li>Fix: List of countries is now always correctly parsed, even when the JSON-file (which is fetched via AJAX) does not have right mime-type.</li>
</ul>
<h4>1.4.0</h4>
<p>Note: <strong>v1.4.0 may break your Countact Form 7-forms containing GatewayAPI-fields</strong>, as the shortode-syntax has slightly changed for most of our fields. We needed to do this change to fix multiple bugs and inconsistencies. Please re-add the GatewayAPI-fields to your Contact Form 7-forms when updating the plugin.</p>
<ul>
<li>
<p>Contact Form 7:</p>
<ul>
<li>Ability to send SMS’es from the frontend.</li>
<li>Updating a subscriber: Forms now only updates groups specifically selected for the form.</li>
<li>Bugfixes and code cleanup, improved shortcode syntax.</li>
</ul>
</li>
<li>
<p>Complete user guide for the system (available online).</p>
</li>
<li>Export of recipients to Excel and CSV-formats.</li>
</ul>
<h4>1.3.3</h4>
<ul>
<li>Contact Form 7: Added support for forms which also contained a reCaptcha-field.</li>
<li>Code cleanup</li>
</ul>
<h4>1.3.2</h4>
<ul>
<li>Bugfix: A menu item had gone missing in the backend.</li>
</ul>
<h4>1.3.1</h4>
<ul>
<li>New UI for creating automated actions. Currently supports “autoreply” based on keyword.</li>
</ul>
<h4>1.3.0</h4>
<ul>
<li>Support for receiving SMS’es added, including setup-wizard and inbox.</li>
</ul>
<h4>1.2.3</h4>
<ul>
<li>Bugfix: The new verification SMS for Contact Form 7 had a typo, breaking verification SMS’es.</li>
<li>Missing translations: The popup-messages related to verification were not translated to danish.</li>
</ul>
<h4>1.2.2</h4>
<ul>
<li>Better international phone numbers support: Prefixed 0’s in the phone number itself (between country prefix and phone number) is now correctly working.</li>
</ul>
<h4>1.2.1</h4>
<ul>
<li>User synchronization:
<ul>
<li>No longer requires a country code meta field, instead allowing a default country code when this value is missing.</li>
<li>Now possible to trigger a “one time” synchronization.</li>
</ul>
</li>
<li>Contact Form 7:
<ul>
<li>Now possible to send an SMS-reply on form success automatically.</li>
<li>SMS-validation for signup, before allowing the form to submit successfully.</li>
<li>Bugfix: Validation now works for all GatewayAPI-fields.</li>
</ul>
</li>
</ul>
<h4>1.2.0</h4>
<ul>
<li>Contact Form 7: Integration supporting signup, update and unsubscribe forms for frontend. Two-factor flow possible for update-flow.</li>
</ul>
<h4>1.1.6</h4>
<ul>
<li>Bugfix: Safari-specific issue with SMS-counter.</li>
<li>Bugfix: Hidden required fields  …</li>
</ul>


GatewayAPI

Send SMS notifications for WooCommerce orders, create SMS campaigns, manage contacts, and add two-factor authentication - powered by GatewayAPI.com.

Swirv vs GatewayAPI