OthviaSign inStart free
← OthviaFor developers

Quickstart

From an empty app to a working sign-in with passkeys and enterprise SSO routing, in four steps.

1. Create a realm

Open the Othvia Console and create a realm for your product. A realm holds its own users, keys, settings and applications. Every new realm starts with a development realm and a production realm, so you can try a configuration before you promote it.

2. Register your application

In the realm, add an application. A web or mobile app is a public client that signs in with the authorization code flow and PKCE. A backend that calls your own APIs is a machine-to-machine client that uses client credentials.

Add the redirect addresses your app uses. Othvia shows the issuer address and the client identifier to copy.

3. Add sign-in to your app

Install the React SDK and wrap your app in the provider. The sign-in component offers passkeys, routes people to their company's single sign-on from their email address, and asks for a second factor when your realm requires one.

bash
pnpm add @othvia/sdk-react
typescript
import { OthviaProvider, SignIn, OrganizationSwitcher } from "@othvia/sdk-react";

export const App = () => (
  <OthviaProvider realm="larkspur">
    <OrganizationSwitcher />
    <SignIn />
  </OthviaProvider>
);

4. Check the session on your server

Your server receives a standard OAuth 2.1 access token and verifies it against the realm's published keys. The SDK's server helper does this in one call. Access tokens can be bound to the client's key with DPoP, so a copied token does not work from another machine.

Next

  • Send a setup link to a customer's IT admin so they can connect their own identity provider.

  • Subscribe to webhooks for connection and directory events.

  • Give an AI agent scoped access through the Management MCP server.