Document extraction

Turn business documents into structured data.

Define the fields your application needs, upload a document, and get validated JSON from a production custom extraction API.

Try it freeView API reference

Credits based on document size · POST /v1/custom-extractors/<id>

Try it freeView API reference

Credits based on document size · POST /v1/custom-extractors/<id>

Get started

Define a schema. Get an endpoint.

Build a custom extractor in the console, then call it like any other Cryvis API.

Open consoleView documentation

Use cases

Built for documents without a pre-built extractor

Define your own schema

Describe the document and write a JSON Schema for the fields your product needs.

Get a production endpoint

Each custom extractor becomes an API you can call with the same auth and metering as built-in types.

Validate against your rules

Field-level formats and soft or hard validation keep output consistent for your application.

Workflow

Replace manual data entry.

Cryvis turns document uploads into custom schema your application can use immediately.

Before

  1. 1Document
  2. 2Human reads it
  3. 3Manual data entry
  4. 4Review
  5. 5System

After

  1. 1Document
  2. 2Cryvis
  3. 3Custom schema
  4. 4Your application

Extracted data

Get the data your application needs.

You define the fields. Cryvis returns them as validated JSON.

Your schema

account_numberbilling_periodamount_due

How it works

Document → Cryvis → Custom schema → Your application

Upload a document, get structured data, and route it into your application.

  1. 1. DocumentDocument
  2. 2. CryvisDocument understanding
  3. 3. Structured dataCustom schema
  4. 4. Your applicationYour application

Capabilities

Technical capabilities

What this custom extraction API supports in production.

  • Structured JSON
  • Typed fields
  • PDF support
  • Image support
  • API keys
  • Usage metering
  • Rate limits
  • Custom schema

API

Integrate it in minutes.

Create an extractor in the console, then call your endpoint with a document upload.

POST /v1/custom-extractors/<id>View API reference

Request

curl -X POST https://api.cryvis.com/v1/custom-extractors/YOUR_EXTRACTOR_ID \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@document.pdf"

Response

{
  "account_number": "48291033",
  "billing_period": "2026-02",
  "amount_due": "94.20"
}

Start building

View API reference →

Why Cryvis

Don't build document-processing infrastructure yourself.

Cryvis handles the document understanding layer so you can focus on your product.

Structured output

Every response is typed JSON your application can store, validate, and route without brittle parsing.

Document-specific extraction

Purpose-built schemas for identity, finance, and vehicle documents — or define your own.

Production API

API keys, rate limits, and usage metering so you ship without building OCR infrastructure.

Related

Explore purpose-built extractors

PassportAutomate identity data capture from passports.Driver's LicenseAutomate customer onboarding from driver's licenses.PAN CardAutomate identity data capture from PAN cards.AadhaarAutomate Aadhaar data capture for digital onboarding.

Ready to build a custom extractor?

Start free. No credit card required.

Create free accountView API reference