Getting Started
Choose Your Integration
You do not need to understand KEYRA internals to pick a path. Start from the outcome you want.
On this page
What are you building?
Primary · OAuth Verify
Use KEYRA as the authentication flow
Start hosted KEYRA passwordless authentication in the browser, then validate the result on your server.
Use OAuth Verify →Partner 2FA
Add KEYRA to an existing login
Keep username/email authentication. Enroll KEYRA as a second factor and run step-up approval at sign-in.
Use Partner 2FA →OAuth Verify
Partner 2FA
Quick comparison
| Question | OAuth Verify | Partner 2FA |
|---|---|---|
| Existing authentication? | Optional — KEYRA can be primary | Yes — keep it |
| Browser involvement | Starts hosted verify with cp_* | Challenge UI only (no secrets) |
| Backend responsibility | Validate result / tokens + create session | Drive enroll/auth APIs + consume result |
| Secrets in browser? | Never | Never |
| Primary credentials | Publishable clientId (cp_*) in browser; server validation | projectId + secret clientId/clientSecret |
| Recommended use | Passwordless primary auth | Step-up / second factor |
| SDKs | @keyra/web-sdk + server SDK / paste script | @keyra/typescript-sdk, Java, Web via proxy |
| API host | https://auth.keyra.ie | |
