SeleID

SeleID SDK

SeleID client SDK

Overview · React Native and Expo · Android · iOS · Register an app · API reference · Errors and security · Changelog

Coming soon @seletech/seleid-client is not on npm yet. These pages describe version 0.1.0 so you can plan an integration. See the roadmap.

The SDK is a dependency-free TypeScript library for serverless and edge runtimes, Node 22+ and React Native or Expo. It talks to https://auth.seleid.dev, validates every response against JSON Schemas, and never hangs: every call has a hard timeout and a typed failure.

What works today and what is planned

CapabilitySDK 0.1.0SeleID server today
Discovery and JWKS fetchBuilt (discovery, jwks)Live
Authorization code exchangeBuilt (exchangeCode)Live, first-party apps only
Refresh with single-flight rotationBuilt (TokenManager)Live, first-party apps only
Token storageBuilt (TokenStore, SecureStoreTokenStore, MemoryTokenStore)Not applicable
Authorize URL and PKCE helperPlanned (not in 0.1.0; see the quickstart for app-side code)Live
Local access-token verificationBuilt (createVerifier)Planned: access tokens are opaque today, not JWTs
Online session check (sessionContext, SessionGuard)BuiltPlanned: /v1/session/context does not exist yet
Devices, preferences, account eventsBuilt (listSessions, revokeSession, revokeAllSessions, getPreferences, patchPreferences, listEvents)Planned: endpoints not deployed
Test doubleBuilt (FakeSeleId)Not applicable
Registered outside apps signing inNot applicablePlanned: apps stay pending review
Native Kotlin and Swift SDKs, a web button, Flutter, Python and PHP librariesPlannedNot applicable
Sandbox with test accounts, sample project, hosted API referencePlannedNot applicable

Because the server pieces marked Planned are not deployed, sessionContext, SessionGuard sensitive checks and local verification return typed errors (for example unauthenticated or unavailable) against production today. The SDK fails closed rather than pretending the account is fine.

Install

Not yet. The command below will work once the package is published; until then it returns a 404 from npm.

npm install @seletech/seleid-client   # planned, not published

How sign-in works

  1. Your app opens https://auth.seleid.dev/authorize in the system browser with a PKCE challenge.
  2. The person signs in and SeleID redirects back to your registered redirect_uri with code and state.
  3. Your app calls client.exchangeCode(...) and stores the returned tokens.
  4. TokenManager refreshes them; SessionGuard checks the session before sensitive actions.

Pick your platform

Last updated 2026-11-12Suggest an editReport a problem with this page