oauth integration

Add sign-in without building another password system.

Let people use their YeboID to sign in to your app. Register the app, connect the documented sign-in steps and send the person back to the right place afterwards.

Read the developer guide Watch the YeboID overview

YeboID overview

One person, more than one role45 sec · English captions

Read the video transcript

One person, a carpenter looking for work, a shop owner selling what he makes, a manager acting for his business. Yebo ID gives him one identity across connected services. He starts with his phone, confirms it's his, and sets a pin. Another service asks for access. He sees what it wants and chooses which business to share. His identity continues. The permissions stay specific. Connected services can receive his verification status when he allows it. Google-style sign-in for Africa, built for the person and the business. Yebo ID, one identity for how Africa works, trades, and builds. Bring Yebo ID into your service.

How to get started

Read the integration guide.
Register your app.
Connect sign-in and the return page.
Check identity and app access.

Use the documented connection

Follow the current integration guide and register the correct return address for your app.

Ask for the right information

Request the profile or verification permissions required by the feature you are building.

Keep your access checks

Validate the identity response, then check the user’s app role and company membership before showing private data.

A few useful details

Ask only for the information the app needs. After sign-in, check the person’s access to your app’s own accounts and company data.

A business dashboard can use YeboID for sign-in and then check which company the person belongs to before loading its invoices.

Use the current documented security requirements. A working sign-in page alone does not protect private app data.

Ready to try it?

Read the developer guide