ASP.NET Core PDF417 Driver License API
Build a minimal ASP.NET Core API that decodes US driver license PDF417 barcodes and returns normalized AAMVA JSON with safe retake handling.
Designing a Safe PDF417 Route in ASP.NET Core
A production ASP.NET Core 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 ASP.NET Core Integration
ASP.NET Core can stream the uploaded image into memory, encode it once, and preserve StructOCR status codes for the client capture flow. 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 ASP.NET Core 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.
ASP.NET Core 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: .NET 8 or later; configure STRUCTOCR_API_KEY on the server
using System.Net.Http.Json;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddHttpClient();
var app = builder.Build();
app.MapPost("/api/license/pdf417", async (IFormFile image, IHttpClientFactory factory) =>
{
if (image.Length > 4_500_000) return Results.StatusCode(413);
await using var stream = image.OpenReadStream();
using var memory = new MemoryStream();
await stream.CopyToAsync(memory);
var http = factory.CreateClient();
http.DefaultRequestHeaders.Add("x-api-key", Environment.GetEnvironmentVariable("STRUCTOCR_API_KEY"));
var response = await http.PostAsJsonAsync("https://api.structocr.com/v1/driver-license-pdf417", new { img = Convert.ToBase64String(memory.ToArray()) });
return Results.Content(await response.Content.ReadAsStringAsync(), "application/json", statusCode: (int)response.StatusCode);
});
app.Run();Technical Specs
- •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417
- •Authentication: x-api-key kept in server-side configuration
- •Inputs: JPG, PNG, or WebP; maximum 4.5 MB
- •Success: Normalized AAMVA JSON with source set to pdf417
- •Recoverable errors: PDF417_NOT_DECODED and AAMVA_NOT_VALID return HTTP 422
- •Cost: 2 credits for a successful decode; processing failures are refunded
Key Features
- •No browser secret: The capture client uploads to your protected backend route.
- •No AI guessing: Unreadable barcodes fail explicitly instead of producing plausible identity values.
- •Data minimization: The route can select only the fields required by the calling workflow.
- •Operational control: Your service owns authorization, logging redaction, retry behavior, and retention.
ASP.NET Core 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
}
}Frequently Asked Questions
Should ASP.NET Core call the PDF417 API from the browser?
No. Keep the StructOCR API key on the server and expose only an authenticated application route to approved clients.
Should the integration retry a 422 response automatically?
No. A 422 normally requires a clearer or correct document image. Ask the user to retake it rather than resending the same input.
Does the endpoint authenticate a driver license?
No. It decodes and parses the AAMVA barcode record. Authenticity and identity decisions require additional controls.
You May Also Like
Related tutorials, platform guides, and comparisons
Maryland Driver License OCR: Extract Fields with Python
Extract visible fields from Maryland driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Utah Driver License OCR: Extract Fields with Python
Extract visible fields from Utah driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Netherlands Driver License OCR: Extract Fields with Python
Extract visible fields from Netherlands driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Cloudflare Workers PDF417 Driver License API
Build an edge API proxy that decodes US driver license PDF417 barcodes and returns normalized AAMVA JSON with safe retake handling.
Australia Driver License OCR with Python SDK
Extract structured fields from a Australia state or territory driver licence with the StructOCR Python SDK and FastAPI.
Brazil Driver License OCR with Node.js SDK
Extract structured fields from a Brazil Carteira Nacional de Habilitação (CNH) with the StructOCR Node.js SDK and TypeScript + Express.
Australia Driver License OCR with Node.js SDK
Extract structured fields from a Australia state or territory driver licence with the StructOCR Node.js SDK and TypeScript + Express.
Brazil Driver License OCR with Python SDK
Extract structured fields from a Brazil Carteira Nacional de Habilitação (CNH) with the StructOCR Python SDK and FastAPI.
AWS Lambda PDF417 Driver License API
Build a serverless AWS Lambda function that decodes US driver license PDF417 barcodes and returns normalized AAMVA JSON with safe retake handling.
Accelerate Auto Insurance Claims with VIN OCR API
Speed up First Notice of Loss (FNOL) and AI damage estimates. Learn how to extract accurate VINs from blurry, user-generated accident photos instantly.
Ohio Driver License PDF417 API
Decode the PDF417 barcode on the back of a Ohio driver license or State ID and return normalized AAMVA fields as structured JSON.
Technical Comparisons & Integrations
Explore platform integrations and competitive analysis
Add Driver's License OCR to Your Bolt.new App in 5 Minutes
Step-by-step guide to integrating the StructOCR Driver's License scanner API into a Bolt.new app. Build car rental and mobility onboarding flows right in your browser.
Add Driver's License OCR using Cursor in 5 Minutes
Step-by-step guide to integrating the StructOCR Driver's License scanner API using the Cursor AI code editor. Build car rental and mobility onboarding flows rapidly.
Add Driver's License OCR to Your Lovable.dev App in 5 Minutes
Step-by-step guide to integrating the StructOCR Driver's License scanner API into a Lovable.dev app. Build car rental and mobility onboarding flows with zero backend.
Add Driver's License OCR to Your Replit App in 5 Minutes
Step-by-step guide to integrating the StructOCR Driver's License scanner API into a Replit application. Build car rental and mobility onboarding flows using Replit Agent and Secrets.
Add Driver's License OCR to Your v0 App in 5 Minutes
Step-by-step guide to integrating the StructOCR Driver's License scanner API into a v0 by Vercel app. Build car rental and mobility onboarding flows with zero backend.
Tesseract & PassportEye vs. StructOCR Passport API
A technical evaluation for developers deciding between open-source MRZ scanners and a dedicated cloud-based Passport OCR API.
From tutorial to production in 5 minutes.
You've seen the code. Now get your API key, grab your 200 free credits, and see it work with your own images. No credit card required.