Skip to content
Developers

Build with WAONA.

Give your users one secure account they already trust. Add “Sign in with WAONA” using open standards and a few lines of code.

Request API accessRead the guide
// app/api/auth/waona/route.ts — send the user to WAONA
import { redirect } from "next/navigation";

export async function GET() {
  const params = new URLSearchParams({
    client_id: process.env.WAONA_CLIENT_ID,
    redirect_uri: "https://yourapp.com/api/auth/callback",
    response_type: "code",
    scope: "openid profile email",
  });
  redirect(`https://id.waona.ke/authorize?${params}`);
}
Built on open standardsOAuth 2.0 and OpenID Connect — the same standards behind every major sign-in. Any library that speaks them works.
Secure by defaultPKCE, short-lived tokens, HTTPS everywhere and scopes that share only what users approve.
Works with your stackNext.js, FastAPI, Django, Laravel, mobile apps — anything that can make an HTTPS request.
Quick start

Four steps to sign-in.

The standard authorization-code flow. If you’ve added Google or Microsoft sign-in before, this will feel familiar.

  1. 01Register your appRequest access and we’ll issue a client ID and secret for your app.
  2. 02Send users to WAONARedirect to the authorize endpoint. Users sign in or create their account once.
  3. 03Exchange the codeYour server swaps the one-time code for tokens over a secure back channel.
  4. 04Read the profileCall userinfo for the name and email the user agreed to share.
Reference

Endpoints & scopes.

Base URL https://id.waona.ke

GET/authorizeStart sign-in and ask the user for consent
POST/tokenExchange a code for access and ID tokens
GET/userinfoRead the signed-in user’s profile
GET/.well-known/openid-configurationDiscovery document for any OIDC library
openidA stable, unique ID for the user
profileName and profile picture
emailVerified email address
Request API accessTell us where to send your client ID and secret. We reply within two working days.