Developers

Continue with Meimo, built like Continue with Google

Standard OAuth 2.0 authorization code flow with PKCE. No proprietary SDK required — any HTTP client can integrate.

Integration in four steps

Register your organization

Create a company account and complete business verification (KYB) — required before your application can request user data.

Create an application

From your organization dashboard, register an application with a redirect URI. You'll get a client ID and client secret.

Redirect to authorize

Send users to app.meimoid.com/oauth-authorize with your client_id, redirect_uri, scope, and a PKCE code_challenge.

Exchange the code

Your backend exchanges the authorization code for an access token server-to-server, then calls userinfo for the granted claims.

Mandatory scopes

“Continue with Meimo” exists to hand your app a verified identity, not an à la carte profile — every integration must request profile and phone. This is enforced server-side, not just documented.

Scope	Claims	Required
identity	meimoId, verified	Optional
profile	fullName, dateOfBirth, picture	Required
phone	phone	Required
email	email	Optional

The authorize URL

A standard, fully-parameterized redirect — nothing proprietary.

https://app.meimoid.com/oauth-authorize
  ?response_type=code
  &client_id=mid_xxxxxxxxxxxxxxxx
  &redirect_uri=https://yourapp.com/callback
  &scope=identity+profile+phone
  &state=RANDOM_STATE
  &code_challenge=CODE_CHALLENGE
  &code_challenge_method=S256

Ready to get a client ID?