The open router for two-factor authentication

OTP once, Passkey forever.

One API that routes each verification across WhatsApp, Telegram, SMS and email, with automatic fallback, then moves returning users to passkeys. Akedly handles delivery, fallback and attack protection, so you integrate once.

Start building See how passkeys work Build with AI agents

What is Akedly

Akedly is a router for verification. Your app makes one call. Akedly picks the channel for each user, sends the code, protects the flow and reports the result. If you know OpenRouter for language models, this is the same idea for two-factor authentication: one integration, many routes behind it.

One API, four channels. WhatsApp, Telegram and SMS, in that default order, with automatic fallback when a channel does not deliver. Email goes out too when you supply an address.
Every channel sends out of the box. SMS, WhatsApp, Telegram and email all send your codes from Akedly's own senders. No setup is needed, so you can integrate in about ten minutes (your first OTP).
Routing that works out of the box. Akedly picks the channel and falls back automatically. You can reorder channels per pipeline, or let users choose on V1.2.
Protection included. Proof-of-work, Turnstile, rate limits and a circuit breaker on V1.2, plus device identity and a managed iframe defense on V2.0.
Passkeys after the first code. On the first success the user can save a passkey, so the next sign-in is a biometric or screen lock instead of a message.

Get your own WhatsApp Business Account

Meta Meta Verified Tech Provider

Akedly is a Meta Tech Provider, so we can help you get your own official WhatsApp Business Account, or connect the one you already have. Your messages then go out under your business name, not Akedly's. If you don't set one up, Akedly sends your OTPs from its own official WhatsApp number, so you can start without one.

Free to get
No monthly fee
No subscription
No annual fee

Getting your account through Akedly is free: no monthly fee, no subscription and no annual fee. You pay only for usage, as on any Akedly account. Meta bills its per-message WhatsApp charge to your account, and Akedly deducts the same amount from your Akedly bill in real time, so you never pay it twice.

Your brand on every code. Recipients see your business name instead of Akedly's.
Required for Utilities. Utility WhatsApp messages are only sent from your own account.
Meta checks your business. Business Verification with company documents usually takes a few business days.

Set up your account Talk to us on WhatsApp

The path in three steps

1. Verify with a code

Start with a one-time code. Integrate the V2.0 widget (recommended) or the V1.2 REST API.

2. Delivered and protected

The code goes out over WhatsApp, Telegram, SMS and email with automatic fallback, behind layered abuse protection: proof-of-work, Turnstile, rate limits and a circuit breaker on V1.2, plus device identity and a managed iframe defense on V2.0.

3. Passkeys from then on

On the first success, the user can save a passkey. Next time a biometric or screen lock is enough: in this app, in other Akedly apps through the Passkey Network Registry, and on other devices.

Choose your authentication method

All three need the same first step: Company Profile and Pipeline Setup, about five minutes.

V2.0 Widget

RECOMMENDED

A hosted verification screen you embed in an iframe. Akedly runs the code flow, captcha, device checks, rate limits and the passkey prompt. You create an attempt on your backend and read the result.

Managed UI with your logo and colors
The widest security tier, including a managed iframe defense layer and device identity
Passkeys with one iframe attribute
Eligible for pay-per-successful-authentication pricing (requirements apply)

Get Started with V2.0

V1.2 REST API

You build the screens and call three endpoints: get a challenge, send the OTP, verify. Akedly Shield adds proof-of-work and Turnstile on the client when the pipeline has them on.

Full UI control, no iframe
Shield SDKs for Web, iOS, Android, Flutter and React Native
Passkeys through a hosted passkey page and your own backend

Pick V1.2 if you cannot embed an iframe or open a system browser.

Get Started with V1.2

V1.0 REST API

SUNSETTING DEC 2026

Legacy. Existing integrations keep working until the sunset on December 30, 2026. New projects should start on V2.0 or V1.2. V1.0 sends OTPs only: no passkeys.

The version of a pipeline is a one-way door: once it is V2, it cannot go back. If you are unsure, create a second pipeline instead of changing a live one.

Passkeys, the end goal

Kill OTP channels before they kill your business.

A user verifies with a code once and saves a passkey. From then on, a biometric or screen lock replaces the code: no WhatsApp, SMS or Telegram message to send, wait for or pay for.

Cheaper

Passkeys cost up to 40% less than an OTP.¹

Faster

One prompt instead of a code round trip.

Harder to phish

There is no code to intercept, and the private key is never shared with your app or with Akedly.

Reusable

Through the Passkey Network Registry, a passkey saved at one Akedly app can be used at another. We are building a reusable network of it.

How passkeys work

The Passkey Network Registry

Authenticator-app codes (TOTP) are superseded by passkeys. The TOTP docs remain for existing pipelines.

¹ With the default passkey rate (60% of your own OTP price for that phone number). Your rate may differ.

Channels

Akedly sends on WhatsApp, Telegram, SMS and email, in that order, with automatic fallback. Nothing needs connecting to start.

Your WhatsApp Business Account — Akedly's shared WhatsApp number sends your OTPs out of the box, except to nine destinations (see the WhatsApp page). Connect your own account to send from your brand number, reach nine more destinations, and send utility WhatsApp.
Your own SMS provider — send on your account and credits, routed per country. The only SMS path Utilities has.

See all channels

Security layers

Every OTP request passes through layers that make abuse expensive and keep real users moving.

Proof-of-work. A computational cost before an OTP is sent, with adaptive difficulty on V1.2.
Cloudflare Turnstile. Bot detection without user friction. Enable it per V1.2 pipeline; the V2.0 widget manages it.
Rate limits. V1.2 limits per phone number, end-user IP when available, and pipeline. V2.0 limits per phone number, device ID and widget.
Circuit breaker. Automatic flood detection with progressive suspension.

V2.0 adds a managed iframe defense layer and device identity. V1.2 does not fingerprint devices on the REST route.

Cluster Gate AI Protection. Coming soon. An AI-powered layer designed to stop coordinated attacks such as SMS pumping before they run up your bill. Read more. Availability may vary by region.

Utilities

Send transactional messages your users did not ask you to verify: order confirmations, shipping updates, appointment reminders. One API call, no verify step.

Sends on your own WhatsApp Business Account and your own SMS provider.
Message content lives in approved templates, not in your code.
A recipient who taps Stop receiving these is suppressed account-wide, on both channels.
Delivery updates, replies and template status changes come back as webhooks.

Start with Utilities

Tutorials

All tutorials
—
Short walkthroughs that take one task from nothing to working.
Add the V2 widget
—
Akedly hosts the whole verification screen. You embed it and read the result.
Send your first OTP
—
From an empty account to a verified code, using the V1.2 REST API. About ten minutes.
Send a utility message
—
Order confirmations, shipping updates, appointment reminders — messages you send, rather than codes you verify.
Receive a webhook
—
Stop polling. Let Akedly tell your server when something happens.

Shield SDKs

Web / JavaScript
—
The @akedly/shield package provides Proof-of-Work solving, Turnstile helpers, and the passkey ceremony launcher for Akedly V1.2.
iOS / Swift
—
AkedlyShield provides Proof-of-Work solving and Turnstile token retrieval for Akedly V1.2 on iOS and macOS.
Android / Kotlin
—
The Akedly Shield SDK for Android provides coroutine-based Proof-of-Work solving and Turnstile token retrieval for Akedly V1.2.
Flutter / Dart
—
The akedly_shield package provides Proof-of-Work solving and Turnstile captcha for Akedly V1.2 in Flutter and Dart.
React Native
—
React Native uses the same @akedly/shield npm package as web.

Testing & going live

Dev Mode & Test Pairs
—
Dev mode lets you drive a complete verification flow — request, deliver, verify — without sending a single message to anyone.
Webhooks
—
A webhook is how Akedly tells your server that something happened — a message was delivered, a customer replied, a verification finished.
Errors
—
This page covers the failure envelope and the handling rules that apply across Akedly.
Pipeline Setup
—
Configure how OTP messages are delivered to your users through customizable pipelines.

Why Akedly

Akedly is not a communications API. It is a purpose-built authentication platform that handles OTP delivery, verification, fraud protection, and channel orchestration as a single service.

Reliability First

Our orchestration algorithm prioritises the most reliable channel to reach your user, with automatic fallback:

WhatsApp → Telegram → SMS → Email

This works nationally (Egypt) and internationally. No configuration needed -- the API handles channel selection, retry logic, and fallback automatically. Our worst-case scenario (SMS fallback) is our competitors' best-case scenario.

Security Suite

Enterprise-grade protection included with every plan:

Name
Captcha Protection
Type
V1.2 / V2.0
Description
Cloudflare Turnstile is configurable per V1.2 pipeline and managed by the V2.0 widget
Name
Device Fingerprinting
Type
V1.2 / V2.0
Description
Not provided by the V1.2 REST route; available at the V2.0 widget level
Name
Rate Limiting
Type
V1.2 / V2.0
Description
V1.2 limits per phone number, end-user IP when available, and pipeline. V2 limits per phone number, device ID, and widget.
Name
Circuit Breaker
Type
V1.2 / V2.0
Description
Automatic flood detection with progressive suspension

Not a Fit For Everyone

Akedly is built for teams that value reliability and security over the cheapest per-message rate. We are probably not the right fit if:

You need custom-formatted verification messages (OTP messages use Akedly's format; for your own transactional text, use Utilities)
You are purely price-sensitive and would choose cheaper over more reliable

For everyone else, we have been a strong fit across 200+ companies actively using Akedly in production.

Developer Experience

15-minute integration with comprehensive guides
Official SDKs for Node.js and Flutter
Webhook callbacks for server-to-server notifications
Real-time analytics and fraud monitoring dashboard
PPS model (Pay-Per-Successful-Authentication) available for trusted, high-volume accounts with clean traffic

How Akedly Compares

Akedly is not a communications API or a bulk SMS provider. We are a purpose-built authentication platform with intelligent delivery orchestration and a full security suite. The distinction matters.

The Problem With Alternatives

Provider	Limitation
Twilio	Prohibitively expensive for Egypt and GCC traffic. Their messaging API bills per message whether or not the authentication succeeds, and the multi-channel orchestration is yours to build.
Firebase OTP	In our own testing we have seen delivery failures to Etisalat numbers and to some Orange numbers in Egypt. No control over delivery channels or fallback logic.
Local SMS providers (SMS Misr, SMS Egypt, etc.)	Communications platforms, not authentication platforms. They hand you an SMS API; the authentication layer around it -- security, rate limiting, fraud protection, delivery fallback -- is yours to build. From our experience, SMS delivery rates are inconsistent at best.

What Akedly Does Differently

Intelligent Orchestration

We do not just send an SMS and hope it arrives. Our algorithm evaluates the best channel for each user in real time:

WhatsApp -- highest delivery and read rates
Telegram -- reaches users where WhatsApp is unavailable
SMS -- universal fallback
Email -- always sent when provided

All automated. No implementation overhead. One API call triggers the entire orchestration. We have not found this combination of WhatsApp + Telegram + SMS fallback offered as a managed service anywhere else.

Full Security Stack

We do not just deliver OTPs -- we protect the entire flow:

Captcha before OTP delivery blocks bots at the gate
Device fingerprinting tracks and scores devices across sessions
Multi-dimensional rate limiting: V1.2 uses phone number, end-user IP when available, and pipeline; V2 uses phone number, device ID, and widget
Circuit breaker auto-suspends under flood attacks
3 additional proprietary layers operating behind the scenes

You get the API, the protection, the guidance, and the expertise. Not just a pipe to push messages through.

Pricing

For international traffic, rates are competitive with bulk deals available. Qualifying high-volume accounts with clean traffic are eligible for PPS (Pay-Per-Successful-Authentication) pricing -- you only pay when the user successfully verifies.