Scanverion for developers
Build your first integration.
Start with one working request, then choose an SDK, CLI, MCP agent integration, collection, or the complete API guide when you need more depth.
Generated from the running .NET API and its typed request and response models.
Download OpenAPI JSONFirst request
Start with the shortest working path.
Set two server-side environment variables, send one document, and inspect the typed response. Choose an SDK or collection after the contract is clear.
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"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 setupPostman
Import, configure, run
The collection contains only AI processing, validation, capability, health, and usage workflows.
- 1
Import both JSON filesSelect Scanverion Local in Postman.
- 2
Set your variablesAdd the API key and absolute sample-file paths.
- 3
Run 00 - SetupCheck health first, then verify the key with capabilities.
- 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-DDusage period
$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"