Use case / Operations

Turn recurring forms into stable fields.

Use descriptions to identify where a value appears and types to define what your system expects from each supported form image.

Start free See a real request and response

Example schema

Ask for the fields that move work forward.

Field names, types, and descriptions travel with every extraction request, so the response matches the object your code already expects.

Schema fields5 fields

company_namecontact_namerequested_start_datepriorityterms_accepted

Response

What your integration receives.

The terminal result for the schema above. Validate it against your own types before writing to a system of record.

extract.tsTypeScript client

const { result } = await client.extractFile({
  file,
  idempotencyKey,
  input: { fileName, mediaType, sizeBytes },
  schema: {
    version: "1",
    fields: [
      { name: "company_name", type: "string" },
      { name: "contact_name", type: "string" },
      { name: "requested_start_date", type: "string" },
      { name: "priority", type: "string" },
      { name: "terms_accepted", type: "boolean" }
    ]
  }
});

terminal resultcompleted

{
  "company_name": "Atlas Field Services",
  "contact_name": "Maya Chen",
  "requested_start_date": "2026-08-03",
  "priority": "standard",
  "terms_accepted": true
}

Production path

From document to validated workflow input.

Name fields using your domain vocabulary.
Add visual descriptions for labels and checkboxes.
Create an authenticated asynchronous extraction job.
Apply business validation before writing to a system of record.

FAQ

Frequently asked questions

Can form schemas include booleans?

Yes. Shared extraction schemas support typed fields, including booleans for values such as visible checkbox states.

Will Routeser enforce my business rules?

Routeser validates extraction output against the schema. Account-specific business rules still belong in your application.

How do I disambiguate two similar labels?

Give each field a description naming the visible label or region it comes from. Descriptions are the cheapest way to separate lookalike fields.

Next step

Run this schema on your own documents

Open the console to define these fields in a workspace and evaluate them against real documents.

Open console