Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dataspike.io/llms.txt

Use this file to discover all available pages before exploring further.

Dataspike supports two common integration patterns for document and identity verification.
Pick the approach that matches your product needs, team resources, and time-to-market.
🔐 Tip: Build and test in Sandbox first (https://sandboxapi.dataspike.io), then switch to Production when you’re ready to go live.

​
Typical Integration Scenarios

Best for: Teams that want a fast, secure, and branded verification flow without building a custom UI from scratch.
  • Use the API to create and manage Applicants and Verifications.
  • Embed the DocVer Web SDK in your app to collect documents, selfies, and liveness checks.
  • The widget handles capture UX, error states, and progression — you control business logic on the backend.
  • Webhooks notify you when the verification completes or changes status.
Start here: See the First Document Verification guide.

​
2) Fully Manual Operation

Best for: Teams that need complete control over UX, have a pre-existing capture flow, or must operate in constrained environments.
  • Build your own client-side UI for document capture and user guidance.
  • Use the API directly to upload files, manage verification state, and trigger proceed when all inputs are ready.
  • Handle all error states and retries in your application.
  • Webhooks still recommended for asynchronous result delivery; polling is available if needed.
You’ll need to implement:
  • Document & selfie capture UI
  • File validation and retry UX
  • API uploads + proceed call
  • Result handling (webhooks or polling)

​
Choosing the right approach

  • Time-to-market: Use API + Web SDK.
  • Full UX control / legacy UI: Choose Fully Manual.
  • Mixed: Start with Web SDK, then override specific steps via API as needed.

​
Next steps