Developer Schema Examples
for Document Workflows

These schema examples show common extraction structures for logistics and insurance workflows. Teams can adapt these packs to match product logic and downstream data systems.

Bill of Lading Schema Pack

{
  "document_type": "bill_of_lading",
  "schema": {
    "header": ["bol_number", "issue_date", "carrier_name"],
    "parties": ["shipper_name", "consignee_name", "notify_party"],
    "route": ["port_of_loading", "port_of_discharge"],
    "cargo_table": ["description", "quantity", "gross_weight"]
  }
}

Medical Certificate Schema Pack

{
  "document_type": "medical_certificate",
  "schema": {
    "person": ["full_name", "document_id"],
    "issuer": ["clinic_name", "physician_name"],
    "period": ["issue_date", "rest_start_date", "rest_end_date"],
    "notes": ["condition_summary", "administrative_remarks"]
  }
}

Invoice Line-Item Schema Pack

{
  "document_type": "invoice",
  "schema": {
    "supplier": ["supplier_name", "tax_id", "invoice_number"],
    "dates": ["invoice_date", "due_date"],
    "line_items": ["description", "quantity", "unit_price", "line_total"],
    "totals": ["subtotal", "tax_amount", "grand_total", "currency"]
  }
}

Frequently Asked Questions

No. These examples show common starting points. Teams can tailor fields and nesting based on their workflow needs.

Yes. Schema definitions can include table arrays, nested objects, and item-level structures for production workflows.

Yes. Teams often use separate schema packs for different document types and business processes.

Examples help align payload structure early so integration endpoints and downstream systems can be wired with less rework.

Get Started Today

Try DocumentLens for free or contact us for an enterprise solution with dedicated support and custom integrations.

Need Enterprise Support?

Submit an inquiry below or email us at support@turbolens.io