Use @authbound/nuxt when you want module setup, auto-imported components, and a verification server route.

Install

Environment

Copy YOUR_POLICY_ID from the Authbound dashboard.

Configure the module

nuxt.config.ts
The module adds these server routes for the browser SDK and server reconciliation. Your secret key and session secret stay server-side. Use these BFF routes with station UI from @authbound/vue when you build station entry or operator flows.
The Nuxt module does not register GET /api/authbound/status or a sign-out (DELETE /api/authbound) route. If your app needs them, add server-side Nitro handlers that read or clear the HttpOnly SDK session cookie.

Verification page

pages/verify.vue

Route protection

By default, the browser SDK calls POST /api/authbound/session after verified status. The Nuxt server route checks the pending verification cookie and same-origin request, fetches the signed verification result from Authbound with your secret key, then creates the HttpOnly Authbound session cookie used by protectedRoutes. SDK-managed sessions require navigator.locks. Same-origin tabs serialize verification creation and session finalization under a lock keyed by the resolved endpoint origin. If you need to support a browser or embedded webview without Web Locks, set sessionMode: "manual" and create the trusted session on your server. For production, use that SDK-managed cookie for same-origin route UX, and process webhooks or signed results to store durable backend state. If you want to own all session creation yourself, set sessionMode: "manual" and create your app session after your trusted webhook or result flow completes.

Next

Review route protection and webhooks before production.