- Collect device signals to strengthen verification and reduce fraud.
- Perform silent verification to verify phone numbers without asking users to enter a code.
SDK keys are publishable, client-side keys — safe to expose. Unlike your backend API key, the SDK key is designed to be embedded in client applications. It is expected to be visible in your browser JavaScript bundle, page source, or mobile app binary, and it is safe to keep in front-end deployment config such as CI/CD pipelines and Helm values.
Use a separate SDK key for each platform. When generating an SDK key in the dashboard, select the device platform (Android, Apple, Web, etc.) that matches your intended use case. Prelude enforces that scoped SDK keys can only be used by matching device platforms, which prevents cross-platform misuse and lets you rotate or revoke a single platform’s key independently.
How device signal collection works
Learn more about each platform’s SDK
Web SDK
Learn how to integrate the Web SDK into your application.
Android SDK
Learn how to integrate the Android SDK into your application.
iOS SDK
Learn how to integrate the iOS SDK into your application.
React Native SDK
Learn how to integrate the React Native SDK into your application.
Flutter SDK
Learn how to integrate the Flutter SDK into your application.