Your user texts a trigger phrase. Hey Pingr auto-replies with your magic link. Your webhook fires. No OTP costs. No passwords.
Integrate once. Your users never touch a password again.
Configure triggers in the dashboard. Listen to events via webhook. That's the entire integration surface.
Built for developers who want to ship fast and scale confidently.
Simple, transparent pricing. Pick a plan and get started in minutes.
Meet them where they are. Add Hey Pingr to your app today — free to start, live in minutes.
Everything you need to know before you integrate.
Hey Pingr is a WhatsApp auto-reply infrastructure service for developers and startups. The flow is simple: you connect your WhatsApp number, configure a trigger phrase (e.g. login) and a reply message (your magic link) in the dashboard — no code needed for the reply itself. When a user texts that phrase, Hey Pingr instantly sends the reply. Simultaneously, a message.received webhook event fires to your server so you can generate a personalised magic link, log the event, or kick off any backend logic. The full webhook integration is available as an npm package (hey-pingr) for Node.js, on PyPI for Python, or as a plain REST API for any other stack. Hey Pingr handles session management, auto-reply delivery, HMAC-signed webhooks, and per-number cooldowns — so you ship auth in an afternoon, not a sprint.
SMS OTP has three structural problems: carrier filtering that causes messages to silently fail, per-message billing that charges even for failed deliveries, and vulnerability to SIM-swap attacks. WhatsApp authentication with Hey Pingr solves all three. Messages are delivered over WhatsApp's end-to-end encrypted network at an average of 3ms — not the 3–45 seconds common with SMS. There are no carrier intermediaries to silently drop messages. In India and Southeast Asia, where WhatsApp penetration exceeds 90% of smartphone users, login completion rates are measurably higher because users already have the app open and notifications on. Cost is also significantly lower: Hey Pingr's Starter plan provides 10,000 messages for $19/month, with overages at $0.002 per message — typically 40–60% less than comparable SMS OTP volume pricing. For any app targeting WhatsApp-dominant markets, the switch pays for itself quickly.
Hey Pingr ships official SDKs for Node.js and Python, both under the package name hey-pingr — available on npm and PyPI respectively. The SDKs provide webhook signature verification so you can safely receive and validate incoming message.received events. The Node.js SDK works with Express, Fastify, NestJS, or any Node framework. The Python SDK supports both sync and async usage, making it compatible with FastAPI, Django, Flask, and asyncio-based apps. For teams using Go, Ruby, PHP, Java, or .NET — webhook verification is a single HMAC-SHA256 check against the x-pingr-signature header, easy to implement in any language. The integration surface is deliberately small: configure triggers in the dashboard, listen on one webhook endpoint — easy to integrate and easy to maintain.
Most developers are live within 10 minutes of creating an account. The setup has four steps: sign up, scan a QR code in the dashboard to connect your WhatsApp number, configure your trigger phrase and auto-reply message, and add a webhook handler to your backend. The webhook handler is a dozen lines using the hey-pingr SDK — install, call verifyWebhook(), read payload.from.phone, done. The quickstart guide covers the full integration including HMAC signature verification and handling disconnection events. Most teams wire it into an existing auth route in an afternoon. All plans include a 7-day free trial so you can complete the integration and test end-to-end before any charges apply.
Hey Pingr is optimised for markets where WhatsApp is the dominant messaging platform — primarily India and Southeast Asia, where over 90% of smartphone users have WhatsApp installed. For users without WhatsApp, we recommend a secondary auth path. The most common pattern is an email magic link fallback: if Hey Pingr returns a failed delivery status via webhook within 10 seconds, your backend automatically triggers the email flow. The webhook payload includes a status field (delivered, failed, read) so your logic can respond precisely. Some customers also use a voice OTP fallback for accessibility. If your user base is primarily outside high-WhatsApp-penetration markets, consider whether Hey Pingr works better as a secondary option alongside email or SMS. The Hey Pingr dashboard shows per-number delivery rates so you can measure actual coverage for your user geography before committing.