Skip to main content
Connect has two API surfaces. Your backend calls the Backend API; the web and native SDKs use the Frontend API for passkey ceremonies.

​
Backend API

Start with authentication and permissions, then implement the two core server operations:
  1. Create a Connect token to authorize enrollment or management for an authenticated user.
  2. Verify signed passkey data before your identity system creates a session after passkey login.
The reference also includes shared user and identifier administration, credentials, passkey ceremonies and events, exports, analytics and Connect configuration. These shared calls support Connect even though their paths do not all begin with /connect. For a standard application integration, start with the two server operations above and the SDK. The shared low-level ceremony calls are available for advanced integration and protocol investigation. Follow the backend integration guide for the complete handoff to your identity system.

​
Frontend API

Replace <ProjectID> with your Connect project ID. Endpoints use /v2/connect/... paths. Use your project’s assigned frontend API configuration if it differs. Use the Web, iOS or Android SDK for client integrations. The advanced frontend reference describes the underlying login, enrollment and management protocol. Your existing identity system owns the application session. A Connect process token or Connect token is not a replacement for that session.

​
Specifications