Skip to main content
📦 GitHub: Dataspike Web Widget SDK

Web SDK Overview

The Dataspike Web SDK (DocVer Widget) enables you to embed document and identity verification directly into your web or mobile web applications.
It provides a secure, customizable user interface that connects to your backend verification flows.
💡 Use case: Let your users complete KYC verification or document upload directly in your product — no redirects required.

Live Demo

You can preview the widget in action here:
👉 Live Demo

Installation

Choose one of the following installation methods: Using NPM
npm install @dataspike/docver-widget
Using Yarn
yarn install @dataspike/docver-widget
Using a script tag
<script src="https://unpkg.com/@dataspike/docver-widget"></script>

Basic Usgae

Basic Usage Render the widget by passing the verification URL ID from your backend:
import { DocsVerificationWidget } from '@dataspike/docver-widget';

const renderWidget = async () => {
  const verificationUrlId = await getVerificationId(); // created on backend
  DocsVerificationWidget({
    id: verificationUrlId,
    elementId: 'root',
    apiUrl: 'https://api.dataspike.io',
  });
};
⚠️ Important: Never expose your API key in frontend code. Always create the verification session on your backend and return only the verificationUrlId to the client.

Backend Integration

Your backend is responsible for securely creating and managing verifications before rendering the widget on the client side.
  1. Create a verification using your Dataspike API key for an existing applicant.
  2. Return only the verificationUrlId to the frontend — this short ID is safe to expose and required for initializing the widget.
  3. Keep sensitive identifiers such as applicantId, profileId, and API keys strictly on the server side.
This approach ensures secure communication between your application and the Dataspike API, while preventing direct client access to privileged data.

Next steps