Docs

Add Sign in with PulseID to your app with the standard OpenID Connect code flow.

PulseID is a standard OpenID Connect provider. Your app sends the person to PulseID, they sign in with the account they already have, and PulseID sends them back with a code that your server trades for tokens. Any OpenID Connect library works, and so do plain HTTP requests. Everything your app needs to know is in the discovery document at https://id.warpulse.com/.well-known/openid-configuration.

Pages

• QuickstartRegister an app, get credentials and run the code flow with PKCE.
• Next.jsAdd Sign in with PulseID to a Next.js app with plain OIDC and PKCE.
• ExpressAdd Sign in with PulseID to an Express app with plain OIDC and PKCE.
• PythonAdd Sign in with PulseID to a Python web app with plain OIDC and PKCE.
• ReferenceEndpoints, scopes, claims, token lifetimes, rules and errors.
• SecretsKeep, rotate with an overlap, and revoke client secrets.
• VerificationWhat WarPulse asks for to verify your organization, and what changes once it does.

Before you start

You need a PulseID account. Create an organization, register an app in it, and you get working credentials at once. Create an organization.