One identity for Africa. Built for your next app.
Your phone number or email gets you in. Your YeboID carries the profile behind it — across the apps you connect, with control over what each one sees. For developers, that means sign-in, verified contact details and consented KYC status through one identity integration.
For African developers connecting people, profiles and services.
One person.
One YeboID.
Your identity, in one place
A profile that connected apps can request permission to use.
You decide what goes with you.
Each app asks for permissions. Your consent controls access.
The identity behind the login
An OTP opens the door. YeboID connects your app to the person, their profile and the verification information they agree to share.
01 / The way in
Start with phone authentication through WhatsApp OTP or SMS verification, according to the app’s settings. Choose email sign-in when it fits, and verify an email address for business workflows. The person keeps one YeboID across connected apps.
02 / The person behind it
With permission, your app can read profile details, phone and email verification, and KYC status. Know whether someone is verified, still being reviewed or not yet verified. A successful login alone is not a KYC check.
03 / Their choice
Ask for the information your product needs. The user approves the requested permissions before you receive their profile data. Signing into one app doesn’t give every other app access to their identity.
One person. More connections.
Start with your phone number or email and complete the sign-in steps shown by YeboID. A returning user with an active session can connect another app without starting from scratch.
See the permissions the app requests. They may cover your profile, verified email or KYC status. Approve what you’re willing to share before continuing.
The app receives its own access to your permitted information. Your next connected app uses the same YeboID, with its own permissions and your consent.
Built for the life around the login
Shopping, working, learning, building a business. People move between services; their identity should move with them. YeboID gives developers in Africa a shared identity foundation, while each app asks only for what it needs.
Each connected app builds its own experience. The person brings the same YeboID and chooses which permissions to grant.
For African developers
Phone verification is the starting point. Your integration can also access consented profile details and KYC verification status, so your app can make its next decision with context.
import { YeboID } from 'yeboid-node';
const identity = new YeboID({
clientId: process.env.YEBOID_CLIENT_ID!,
});
// After sign-in, read consented claims.
const person = await identity.getUserInfo(
accessToken,
);
person.sub; // Stable person ID
person.emailVerified; // With email scope
person.kycStatus; // With kyc scopeUserinfo example after token exchange. Fields depend on granted permissions and available profile data. Follow the guide for PKCE, your callback and API authorization.
Developer questions, answered
Register an OAuth application with YeboID, configure your callback URL and connect to hosted sign-in using an SDK or OAuth 2.0 with PKCE. YeboID handles phone entry and OTP verification, then returns the user to your app.
Phone authentication integration guide ↗The login connects your app to a reusable identity. With the user’s consent, you can request profile details, verified contact information and KYC status. Other apps connected to YeboID use the same person identifier, with separate permissions for each app.
Explore identity permissions ↗A user enters their phone number and receives a one-time passcode on WhatsApp. Entering that code confirms access to the number as part of authentication. The connected app’s settings determine whether WhatsApp is preferred or required.
Explore the authentication flow ↗Yes, when the connected application allows it. YeboID supports WhatsApp-first, WhatsApp-required and SMS-only configurations. SMS is not offered for an application that requires WhatsApp verification.
Read the sign-in documentation ↗Yes, with the user’s consent and the kyc scope. Your app can receive their KYC verification status, including when they are not yet verified. Full identity verification data requires the separate kyc:full permission. Phone OTP verification alone does not establish KYC verification.
Understand KYC scopes and consent ↗Users confirm an email address with a code sent to their inbox. After sign-in, request the email scope to read the permitted email and email_verified claims. Your app can check that status before granting access to business features. The hosted login offers both phone and email sign-in.
Read about verified email ↗No. Each connected app requests its own permissions. The user must approve them before the app can read the corresponding profile data. A shared sign-in doesn’t give an app access to every field or action.
See how permissions work ↗Keep personal information in YeboID and store the stable YeboID user identifier in your app. Fetch permitted profile fields through userinfo. Users can review and revoke connected-app access from their YeboID account.
Review profile access and revocation ↗More practical reading in our identity and authentication guides.
Build the next connection