Skip to content

Scanverion for developers

API documentation

Request contracts, SDK examples, and integration guides for document extraction, face and signature comparison, camera liveness, and reusable face templates.

Live API contractOpenAPI 3.1.1 / v1

Generated from the running .NET API and its typed request and response models.

Download OpenAPI JSON

Quickstart

Create a key, set two environment variables, and send a verified first request.

Server-side credential. Send Authorization: Bearer skv_.... Never embed a key in browser JavaScript, a mobile binary, analytics, or logs.
Requestbash
export SCANVERION_API_URL="https://api.scanverion.com"
export SCANVERION_API_KEY="skv_..."

curl --request POST "$SCANVERION_API_URL/api/v1/ai/document-processing" \
  --header "Authorization: Bearer $SCANVERION_API_KEY" \
  --header "Idempotency-Key: first-document-001" \
  --form "File=@document.jpg;type=image/jpeg" \
  --form "Operations=Scanner"

Browse the integration guide · Response model · Errors and retry strategy

Getting started

Documents and images

Identity and biometrics

  • Face comparison

    Compare two authorized portraits independently of document detection, with similarity, face geometry, and review reasons.

  • Liveness

    A short camera session checks for presentation attacks. Face matching remains a separate assessment.

  • Signature comparison

    Compare one candidate signature with three to five references for experimental visual similarity.

  • Face templates and database search

    Integrate reusable signed face templates, store one vector per person and search your own database with pgvector.

Usage and reliability

Reference and tools

  • OpenAPI reference

    Open the generated Scalar explorer or download the machine-readable contract.

  • MCP integration

    Hosted OAuth connections, client registration, scopes, and local stdio setup for VS Code and Claude Desktop.

SDKs, CLI and collections

Developer tooling

Choose a path. Ship the same contract.

Move from a sample to a verified server-side request with one API contract across every tool.

MCP setup
Server-side keys onlyNever put a Scanverion API key in browser code. These examples run from a trusted backend or terminal.
  1. 1Try a document
  2. 2Create a scoped key
  3. 3Run your first request
  4. 4Inspect usage

Postman

Import, configure, run

The collection contains only AI processing, validation, capability, health, and usage workflows.

  1. 1

    Import both JSON filesSelect Scanverion Local in Postman.

  2. 2

    Set your variablesAdd the API key and absolute sample-file paths.

  3. 3

    Run 00 - SetupCheck health first, then verify the key with capabilities.

  4. 4

    Choose a workflowRun Document AI, Vehicle AI, Validation, or Usage.

baseUrl
https://api.scanverion.com
apiKey
skv_... processing key
sampleDocument
Absolute PDF or image path
sampleDocument2
Second file for batch requests
sampleVehicle
Absolute vehicle image path
fromDate / toDate
YYYY-MM-DD usage period
No package required
$env:SCANVERION_API_URL = "https://api.scanverion.com"
$env:SCANVERION_API_KEY = "skv_..."

curl.exe --request POST "$env:SCANVERION_API_URL/api/v1/ai/document-processing" `
  --header "Authorization: Bearer $env:SCANVERION_API_KEY" `
  --header "Idempotency-Key: first-request-001" `
  --form "File=@invoice.pdf;type=application/pdf" `
  --form "Operations=Scanner"