Add a login button to your app that signs people in with their WS Mail account. Standard OpenID Connect, verified email addresses, and with the user’s consent, whether they are a verified professional.
The first sign-in creates the account in your app from details we have already confirmed, the same way “Sign in with Google” works.
Ask for the ws.verified scope and learn whether the person holds a live verified badge: a credential check reviewed by a person, not a checkbox.
An address is asserted only after it has been confirmed, so the email in the token is one the user actually controls.
Authorization code flow with mandatory PKCE, a discovery document and a JWKS, so any OIDC library works. Tokens say whether two-factor sign-in was used.
A consent screen names your app and exactly what it will receive before the user returns to you.
A full guide with working code, and a prompt that hands the whole integration to an AI coding assistant.
Apps for clinicians, lawyers and other licensed professionals usually rebuild the same thing: a sign-up form, an email confirmation, and then a manual check that the person really holds the licence they claim. With Sign in with WS Mail, that check has already been done. A person reviewed the credential, and the badge is published on a public verification page the user controls.
Your app asks for the ws.verified scope, the user sees exactly that on the consent screen, and the ID token tells you whether they hold a live badge. You still decide what a verified user may do in your app; we only tell you what we checked.
Register the app in the admin console, receive a client ID (and a secret for server-side apps), and point any OpenID Connect client at our discovery document. Single-page and mobile apps register as public clients and rely on PKCE alone. The developer guide walks through every request, token verification, and creating the user on first sign-in.
A login button for your app, like “Sign in with Google”, built on standard OpenID Connect. Users sign in with their WS Mail account, and your app receives their name and verified email, plus whether they hold a verified professional badge if you ask for it and they agree.
Any OpenID Connect client. Point it at the discovery document and use the authorization-code flow with PKCE; the developer guide has copy-paste code and an AI prompt for your coding assistant.
That the person passed a credential review: for clinicians, a check against the public NPI registry reviewed by a person. It is shared only with the user’s consent, on the consent screen they see before returning to your app.
Create a free account, register your app in the admin console, and follow the guide. Integration is free.
Create your free accountNo credit card. No trial clock.