Skip to content
Akedly

MetaMeta Verified Tech Provider

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.

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 integration, or let users choose on Headless.
  • Protection included. Proof-of-work, Turnstile, rate limits and a circuit breaker on Headless, plus device identity and a managed iframe defense on Gateway.
  • 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


The path in three steps

1. Verify with a code

2. Delivered and protected

3. Passkeys from then on


Choose your authentication method

All three need the same first step: Company profile and your first integration, about five minutes.

V1.0 REST API

SUNSETTING DEC 2026

An integration's type is fixed when you create it. To switch, create a new integration of the other type and move your traffic to it, or upgrade a headless integration to V2.0 in one step. Gateway was called V2.0 Widgets and Headless was the V1.2 REST API; Integrations explains the names.


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

Faster

Harder to phish

Reusable

How passkeys work

The Passkey Network Registry

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

¹ 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 and SMS, in that order, with automatic fallback; when the request has an email address, the code also goes by email, once, with the first phone attempt. 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 one-way WhatsApp.
  • Your own SMS provider — send on your account and credits, routed per country. The only SMS path One-way messaging has.

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 Headless.
  • Cloudflare Turnstile. Bot detection without user friction. Enable it per headless integration; the gateway screen manages it.
  • Rate limits. Headless limits per phone number, end-user IP, and integration. Gateway limits per phone number, device ID and gateway screen.
  • Circuit breaker. Automatic flood detection with progressive suspension.

Gateway adds a managed iframe defense layer and device identity. Headless does not fingerprint devices on the REST route.

Cluster Gate AI Protection. An AI-powered layer, on for every Headless and gateway integration by default, designed to stop coordinated attacks such as SMS pumping before they run up your bill. Read more. Availability may vary by region.


One-way messaging

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.

Tutorials

  • All tutorials

    —

    Short walkthroughs that take one task from nothing to working.

  • Add a gateway screen

    —

    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 Headless REST API. About ten minutes.

  • Send a one-way 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 Headless.

  • iOS / Swift

    —

    AkedlyShield provides Proof-of-Work solving and Turnstile token retrieval for Akedly Headless 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 Headless.

  • Flutter / Dart

    —

    The akedly_shield package provides Proof-of-Work solving and Turnstile captcha for Akedly Headless 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.

  • Integrations

    —

    Configure how OTP messages are delivered to your users through customizable integrations.


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

Protection included with every plan:

  • Name
    Captcha Protection
    Type
    Headless / Gateway
    Description

    Cloudflare Turnstile is configurable per headless integration and managed by the gateway screen

  • Name
    Device Fingerprinting
    Type
    Headless / Gateway
    Description

    Not provided by the Headless REST route; available at the gateway screen level

  • Name
    Rate Limiting
    Type
    Headless / Gateway
    Description

    Headless limits per phone number, end-user IP, and integration. Gateway limits per phone number, device ID, and gateway screen.

  • Name
    Circuit Breaker
    Type
    Headless / Gateway
    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 One-way messaging)
  • 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

ProviderLimitation
TwilioProhibitively 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 OTPIn 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:

  1. WhatsApp -- highest delivery and read rates
  2. Telegram -- reaches users where WhatsApp is unavailable
  3. SMS -- universal fallback
  4. 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: Headless uses phone number, end-user IP, and Integration; Gateway uses phone number, device ID, and gateway screen
  • 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.


Getting Started