Web Integration (Optional)

Overview

Trigger Reclaim verification from your website through an installed browser extension. Users can verify without leaving your site - the extension handles all verification logic.

When to Use This

Choose web integration if:

• 🌐 You have a website (not building an extension)
• 🔌 Users have a compatible extension built with this SDK
• 🎨 You control the website UI (extension handles verification)
• 🔄 You want in-page verification without redirects

How It Works

The web integration establishes communication between your website and the Reclaim browser extension:

Flow Breakdown

1. Your Website: Calls SDK with extension ID
2. Content Script Bridge: Receives request from webpage
3. Extension Background: Orchestrates verification
4. Offscreen Document: Generates proofs
5. Provider Tab: Handles authentication
6. Proofs Returned: Sent back to your website

Get Your API Credentials First

Prerequisites

Before integrating, ensure you have:

• ✅ Completed the Installation guide
• ✅ Obtained your API credentials (APP_ID and APP_SECRET) from the API Key guide
• ✅ Access to a Reclaim-compatible browser extension (or built one using Extension Integration)
• ✅ A web application (React, Vue, vanilla JavaScript, etc.)

Key Differences from Extension Integration

Extension ID

The most important configuration for web integration is the Extension ID. This identifies which browser extension will handle verification requests.

Finding the Extension ID

For Chrome extensions:

1. Navigate to chrome://extensions
2. Enable "Developer mode" (top-right toggle)
3. Find the extension
4. Copy the ID (shown under the extension name)

Example ID: abcdefghijklmnopqrstuvwxyz123456

Storing the Extension ID

Development:

// .env.local
VITE_RECLAIM_EXTENSION_ID=abcdefghijklmnopqrstuvwxyz123456

Production:

// Use environment variables or configuration
const EXTENSION_ID = process.env.REACT_APP_RECLAIM_EXTENSION_ID;

Architecture Benefits

For Developers

• ✅ No Extension Development: Just integrate SDK in your web app
• ✅ Faster Integration: Standard web development workflow
• ✅ Framework Agnostic: Works with React, Vue, Angular, vanilla JS
• ✅ Easier Updates: Update your website without extension review process

For Users

• ✅ Single Extension: One extension works across multiple websites
• ✅ No Page Reloads: Verification happens in-place
• ✅ Trusted Source: Extension from verified publisher
• ✅ Consistent UX: Familiar verification flow across sites

Security Considerations

Extension Trust

Users must trust the browser extension since it:

• Handles sensitive authentication flows
• Generates cryptographic proofs
• Has access to provider credentials

Best Practices:

• Use well-known, audited extensions
• Clearly communicate which extension is required
• Provide extension installation instructions
• Verify extension authenticity

Website Security

Your website should:

• Validate proofs server-side (never trust client-side proofs alone)
• Use HTTPS for all communication
• Implement Content Security Policy (CSP)
• Handle extension not installed gracefully

Browser Compatibility

Web integration works in browsers supporting Chrome extensions:

Integration Approaches

You have two approaches for web integration:

1. Direct Client-Side Integration (Quick Start)

Pass credentials directly in your frontend code. Not recommended for production.

Pros:

• ✅ Fastest to implement
• ✅ No backend required
• ✅ Good for prototypes

Cons:

• ❌ Exposes application secret
• ❌ Not secure for production
• ❌ Credentials visible in client code

Quick Start Guide →

2. Server-Side Configuration (Production)

Generate verification requests on your backend, only pass configuration to frontend.

Pros:

• ✅ Secure - secrets stay on server
• ✅ Backend validation
• ✅ User authorization
• ✅ Production-ready

Cons:

• ❌ Requires backend API
• ❌ More complex setup

Production Setup →

Example Use Cases

DeFi Applications

Verify user credentials before token operations:

// Verify Twitter account before claiming tokens
const proofs = await verifyWithReclaim("twitter-profile");
await claimTokens(proofs);

Social Platforms

Authenticate users with provider credentials:

// Verify GitHub account for developer community
const proofs = await verifyWithReclaim("github-login");
await createProfile(proofs);

Identity Verification

Proof of account ownership:

// Verify Google account ownership
const proofs = await verifyWithReclaim("google-login");
await linkAccount(proofs);

Next Steps

Proceed to setup and implementation:

1. Setup - Configure SDK in your web application
2. Usage - Implement verification flows
3. Troubleshooting - Common issues and solutions

Extension Installation Guide

For users of your website, provide clear instructions:

### Install the Reclaim Extension
 
1. Visit the [Chrome Web Store](https://chrome.google.com/webstore)
2. Search for "Reclaim Protocol"
3. Click "Add to Chrome"
4. Return to this page and click "Verify"

Or detect and prompt automatically (covered in Usage guide).