Express PDF417 Driver License API

Designing a Safe PDF417 Route in Express

A production Express integration must protect the API key, reject oversized uploads, preserve enough image quality for decoding, and translate recoverable 422 responses into a useful capture experience. A browser-only request would expose credentials and make abuse controls harder.

A Server-Side Express Integration

Express and Multer can hold the upload in memory, reject oversized files, and send the Buffer through the official Node.js SDK. The PDF417 API reference documents the complete response and error model. Identity fields are only returned after deterministic barcode decoding and AAMVA parsing.

Where This Workflow Fits

• Protected upload endpoint: Keep STRUCTOCR_API_KEY inside Express server configuration rather than client code.
• Structured form prefill: Map normalized AAMVA fields into an editable form and require user or staff confirmation.
• Recoverable retake flow: Turn PDF417_NOT_DECODED into a clear request for a sharper, complete license-back image.

Express PDF417 Endpoint

The example accepts image data on the server and calls /v1/driver-license-pdf417. Adapt authentication, authorization, rate limits, and retention to your application.

Prerequisite: npm install structocr express multer

const express = require("express");
const multer = require("multer");
const StructOCR = require("structocr");

const app = express();
const upload = multer({ storage: multer.memoryStorage(), limits: { fileSize: 4_500_000 } });
const client = new StructOCR(process.env.STRUCTOCR_API_KEY);

app.post("/api/license/pdf417", upload.single("image"), async (req, res) => {
  if (!req.file) return res.status(400).json({ error: "image is required" });
  try {
    return res.json(await client.scanDriverLicensePdf417(req.file.buffer));
  } catch (error) {
    return res.status(error.status || 502).json({ error: error.code, message: error.message });
  }
});

app.listen(3000);

Express Response Shape

The example contains fictional identity values. Optional AAMVA elements can be null, and production logs should avoid storing raw identity data.

{
  "success": true,
  "data": {
    "type": "drivers_license",
    "source": "pdf417",
    "country_code": "USA",
    "region": "CA",
    "document_number": "SAMPLE1234",
    "surname": "SAMPLE",
    "given_names": "ALEX MORGAN",
    "first_name": "ALEX",
    "middle_name": "MORGAN",
    "sex": "X",
    "date_of_birth": "1990-01-15",
    "date_of_issue": "2025-01-15",
    "date_of_expiry": "2030-01-15",
    "address": "100 EXAMPLE AVE",
    "city": "SAMPLE CITY",
    "postal_code": "00000",
    "vehicle_class": "C",
    "restrictions": null,
    "endorsements": null,
    "document_discriminator": "SAMPLE-DISCRIMINATOR",
    "issuer_identification_number": null,
    "aamva_version": 10,
    "jurisdiction_version": 0
  }
}