Description
Sendity connects WordPress to Sendity Cloud or your own Sendity server. Visitors send a short code from their WhatsApp or mail app, and Sendity confirms who sent it. The plugin provides a Sendity Login editor block and [sendity_login] shortcode, can appear on wp-login.php, and validates signed Sendity authorizations before starting a normal WordPress session.
Features
- Bundle Sendity Client 0.4.3 locally; no runtime CDN or remote JavaScript.
- Verify phone numbers via WhatsApp, with an explicit SMS fallback when the campaign allows it.
- Show a clear notice instead of a generic error when a Sendity campaign is paused or out of credit.
- Discover public signing keys through JWKS discovery using the WordPress HTTP API.
- Require a valid signature, issuer, audience, pairwise subject, separate auth-request/token IDs, expiry, auth time, AMR/channel, and standard verified email or phone claims.
- Reject replayed or oversized login tokens.
- Create or reuse low-privilege WordPress users only for verified email identities.
- Support verification-only campaigns, including campaigns that verify phone numbers, without creating WordPress users or sessions.
This plugin is a WordPress integration, not a Sendity server.
External services
By default, this plugin connects visitors’ browsers to Sendity Cloud, an external verification service operated by Dachs Consulting GmbH. A site administrator can instead configure a self-hosted Sendity server.
When verification starts, the browser sends the Sendity Campaign ID (public key), site origin, localized interface templates, and transport configuration to the configured Sendity server. Normal web requests also disclose technical data such as the visitor’s IP address and user agent. The visitor then sends the displayed code through the configured channel, which may disclose the email address or phone number being verified to that Sendity service and the relevant email or telecommunications provider. Short-lived authentication request data, including the request ID and client secret, is stored in browser session storage for the flow.
For WordPress login campaigns, Sendity returns a signed authorization containing the verified email address and potentially profile data supplied through the verification channel. The plugin fetches public signing keys from the configured JWKS endpoint, verifies the authorization locally, prevents replay, creates or reuses the WordPress user, and stores verification metadata as user meta. WordPress passwords and administrator credentials are never sent to Sendity.
When a campaign verifies phone numbers via WhatsApp, the visitor’s WhatsApp app sends the code through WhatsApp (Meta). WhatsApp Terms of Service: https://www.whatsapp.com/legal/terms-of-service and Privacy Policy: https://www.whatsapp.com/legal/privacy-policy
For Sendity Cloud:
- Terms of Service: https://sendity.io/terms
- Privacy Policy: https://sendity.io/privacy
- Service website: https://sendity.io
For a self-hosted Sendity server, that operator’s terms and privacy policy apply.
Source code and bundled assets
WordPress integration source: https://gitlab.com/sendity/integrations/wordpress
Bundled Sendity Client source: https://gitlab.com/sendity/client/custom-element/-/tree/v0.4.3
The release ZIP includes the generated browser bundle so WordPress does not need Composer, npm, or an external CDN at runtime. Exact source revision, checksum, build command, license, and dependency notices are included in assets/sendity-client/SOURCE.md and assets/sendity-client/THIRD-PARTY-NOTICES.md.
Configuration
Important options under Settings -> Sendity:
- Sendity Campaign ID: the Campaign ID from the Sendity campaign settings. The Client still receives it as the
public-keyattribute. - Campaign Purpose:
WordPress login (email)orVerification onlyfor campaigns such as phone verification. - Show on wp-login.php: available for WordPress login campaigns.
- Create WordPress Users: create a low-privilege user after verified email login; enabled by default.
- Default Role for New Users: defaults to
subscriber; privileged roles are unavailable. - Login Redirect: defaults to
/. - Server URL: defaults to
https://sendity.io/api; change only for a self-hosted server. - JWKS URL Override: optional; leave empty for automatic JWKS discovery.
- Transport:
Autois recommended. - Replay TTL: how long used authorizations are remembered.
Constants such as SENDITY_SERVER_URL, SENDITY_ISSUER, SENDITY_AUDIENCE, SENDITY_APP_PUBLIC_KEY, and SENDITY_JWKS_URL may be defined in wp-config.php.
Installation
- Install and activate Sendity from
Plugins -> Add New, or upload the plugin ZIP. - Open
Settings -> Sendity. - Paste the Sendity Campaign ID.
- Select the Campaign Purpose that matches the Sendity campaign.
- Add the
Sendity Loginblock or[sendity_login]shortcode. For email login campaigns, you may also enablewp-login.phpintegration.
FAQ
How do I add Sendity to content?
Add the Sendity Login block, or use [sendity_login]. Presentation attributes remain available, for example [sendity_login variant="modal" position="top" sendity_border_radius="1.25rem"]. Security-sensitive server URL, public key, and transport values always come from plugin settings and cannot be overridden by shortcode content.
Can a phone-verification campaign create WordPress users?
No. Select Verification only as the Campaign Purpose and disable session handoff for that campaign in Sendity. The block or shortcode can perform verification, but the plugin suppresses wp-login.php, user creation, and WordPress session handoff. WordPress login mode also rejects any signed result whose verified identifier and channel are not email.
How are WordPress users created?
Only a signed result for a verified email identity can create a user. The token must pass signature, issuer, audience, expiry, subject, token-ID, key, and replay checks first. The default role is subscriber; privileged roles are not offered. Disable user creation to allow existing users only.
Can I use my own Sendity server?
Yes. Configure the Server URL and, if needed, the JWKS URL. Your server must issue authorizations compatible with the documented Sendity contract.
Does Sendity receive WordPress passwords?
No. Sendity performs channel verification. WordPress verifies the signed result and uses WordPress core APIs for users, roles, cookies, and sessions.
How are translations provided?
The plugin and bundled client contain English source and fallback strings only. All settings, block editor, login errors, accessibility labels, and visitor-facing Sendity interface strings use the sendity text domain. After publication, WordPress.org generates and distributes community language packs from translate.wordpress.org. No translation catalog or separate client translation pack is bundled in the plugin ZIP.
Screenshots
Changelog
0.2.2
- Update Sendity Client to 0.4.3: the sign-in widget replaces an expiring code on its own, so visitors no longer have to request a new one. A message that is already on its way with the previous code still signs them in.
0.2.1
- Update Sendity Client to 0.4.1: the send buttons say what they do (“Send email”, “Send WhatsApp”, “Send message”).
0.2.0
- Update Sendity Client to 0.4.0 with the new Sendity design, the animated signet, and the formal German address in client defaults.
- Verify phone numbers via WhatsApp with an explicit SMS fallback; all new WhatsApp texts are translatable.
- Explain unavailable campaigns (for example when credit is exhausted) instead of showing a generic error.
- Rename apps to campaigns in settings and documentation; the Campaign ID replaces the App Public Key label.
- Refresh the settings page, block icon, and block preview (WhatsApp and unavailable states) in the new Sendity design.
0.1.3
- Update Sendity Client to 0.3.4 and reliably resume verification after switching to the messages or mail app.
- Tell SMS users to return to their browser without a misleading hostname link.
0.1.2
- Declare Block API version 3 compatibility for the iframed WordPress 7.1 editor.
- Confirm compatibility with WordPress 7.1.
0.1.1
- Update the bundled Sendity Client to 0.3.3.
- Let the Client drawer expand from the top, center, or bottom according to its position.
0.1.0
- Initial WordPress.org release with Sendity Client 0.3.2.
- Add block, shortcode, and optional
wp-login.phpintegration. - Add signed authorization verification, JWKS discovery, and replay protection.
- Add explicit verification-only mode for non-email apps.



