Quickstart
Get started quickly with client-side Reclaim SDK integration for prototyping and learning
⚠️ Development Only - Not for Production
This quickstart guide shows client-side initialization which exposes your APP_SECRET in the browser. This approach is only suitable for:
- Learning and prototyping
- Local development
- Proof-of-concept demos
Never deploy this to production. For production applications, use the Backend Integration with secure backend initialization.
Overview
The quickstart approach lets you experience the Reclaim verification flow in minutes by initializing the SDK directly in your frontend code. This is the fastest way to understand how the SDK works, but it's not secure for production use.
Quick Example Available
Looking for a simple React example to try immediately? Check out the Quick Start section on the main JS SDK page for a practical React component you can use right away.
This page provides additional examples for vanilla JavaScript, Vue, and alternative integration methods.
Prerequisites
- ✅ Installed the SDK following the Installation guide
- ✅ Obtained your
APP_ID,APP_SECRET, andPROVIDER_IDfrom the API Key guide - ✅ A React or vanilla JavaScript project set up
Two Integration Methods
There are two ways to trigger verification in your frontend:
Method 1: triggerReclaimFlow() (Recommended)
The triggerReclaimFlow() method automatically detects the user's platform and provides the optimal verification experience. This is the simplest approach.
What it does:
- Automatically shows QR code modal on desktop
- Redirects to App Clip on iOS
- Redirects to deep link on Android
- Uses browser extension if available
Method 2: getRequestUrl() (Manual Control)
The getRequestUrl() method gives you the verification URL to display however you want. Use this when you need custom UI or specific flow control.
What it does:
- Returns a verification URL
- You handle displaying it (QR code, link, button, etc.)
- More control over the user experience
React Implementation
Method 1: Using triggerReclaimFlow()
Method 2: Using getRequestUrl()
QR Code Library: Install react-qr-code for Method 2:
Vanilla JavaScript Implementation
Method 1: Using triggerReclaimFlow()
Method 2: Using getRequestUrl()
Security Considerations
Why This Isn't Production-Ready
When you initialize the SDK in the browser:
- APP_SECRET is exposed - Anyone can view your secret in the browser's DevTools
- No backend verification - Proofs aren't verified server-side before use
- Client can be tampered - Users could potentially modify the verification flow
- Credentials can be stolen - Your API credentials are visible in the source code
The Fix: Use backend initialization to keep APP_SECRET secure on your server.
What's Next?
After experimenting with the quickstart:
- Backend Integration → - Learn how to securely initialize from your backend ⭐
- Backend Verification → - Verify proofs server-side
- API Reference → - Explore all SDK methods
Common Issues
Modal Doesn't Appear
Issue: Nothing happens when calling triggerReclaimFlow()
Solution: Check browser console for errors. Ensure you're calling it from a user interaction (button click).
QR Code Not Loading
Issue: QR code is blank or shows an error
Solution: Verify your credentials are correct and the provider ID is valid.
Mobile Verification Fails
Issue: App Clip or deep link doesn't launch on mobile
Solution: Test on an actual mobile device. Simulators may not support App Clips or deep links.
For more help, see the Troubleshooting Guide.