Spring Boot PDF417 Driver License API

Designing a Safe PDF417 Route in Spring Boot

A production Spring Boot 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 Spring Boot Integration

Spring Boot can validate multipart input and relay the normalized response while leaving barcode decoding and AAMVA parsing to the API. 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 Spring Boot 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.

Spring Boot 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: Java 21 and Spring Boot 3; configure STRUCTOCR_API_KEY on the server

@RestController
@RequestMapping("/api/license")
class Pdf417Controller {
  private final RestClient client = RestClient.builder()
      .baseUrl("https://api.structocr.com")
      .defaultHeader("x-api-key", System.getenv("STRUCTOCR_API_KEY"))
      .build();

  @PostMapping(value = "/pdf417", consumes = MediaType.MULTIPART_FORM_DATA_VALUE)
  String decode(@RequestPart MultipartFile image) throws IOException {
    if (image.getSize() > 4_500_000) throw new ResponseStatusException(HttpStatus.PAYLOAD_TOO_LARGE);
    Map<String, String> payload = Map.of("img", Base64.getEncoder().encodeToString(image.getBytes()));
    return client.post().uri("/v1/driver-license-pdf417")
        .contentType(MediaType.APPLICATION_JSON)
        .body(payload)
        .retrieve().body(String.class);
  }
}

Spring Boot 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
  }
}