Utah Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Utah driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
Reading Utah Card Barcodes in Real Workflows
Utah fintech companies onboard customers remotely, and ski resorts serve visitors from many states. Remote photos are often small screenshots instead of camera originals. PDF417 error correction recovers some damage, but an application should never invent identity values when the barcode cannot be decoded.
One API for Utah Licenses and ID Cards
Utah cards are issued by the Utah Driver License Division. Licenses and identification cards carry the same AAMVA DL/ID PDF417 barcode on the back. Send the back image to the StructOCR PDF417 API: it decodes the barcode deterministically, normalizes the jurisdiction to UT, and returns document_kind as driver_license or id_card. Test a non-sensitive sample in the free PDF417 scanner. For the printed front of the card, use the Driver License OCR API.
Where This Workflow Fits
- Fintech account opening: Pre-fill names, dates, and address for fintech account opening and keep final confirmation in your application.
- Ski rental agreements: Accept both Utah licenses and state ID cards, and use document_kind where only a license is acceptable.
- Medical cannabis pharmacies: Send unreadable Utah barcodes to a retake or manual review step instead of saving partial identity data.
Decode a Utah Card Back
Upload a JPG, PNG, or WebP image of the full card back. Keep the API key on your server, accept the upload in your backend, and return the capture_issue hint to the user when decoding fails.
Prerequisite: A server-side StructOCR API key and a clear image of the complete card back
curl -X POST https://api.structocr.com/v1/driver-license-pdf417 \
-H "x-api-key: $STRUCTOCR_API_KEY" \
-F "file=@utah-card-back.jpg"Technical Specs
- •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417
- •Document scope: Back of a Utah driver license or state ID card with an AAMVA PDF417 record
- •Inputs: JPG, PNG, or WebP; Base64 JSON or multipart upload; maximum 4.5 MB
- •Cost: 2 credits for a successful decode; processing failures are refunded
- •Region output: UT when encoded in a valid Utah record; document_kind separates licenses from ID cards
- •Important: Parsing barcode data does not by itself authenticate the credential or the person presenting it
Key Features
- •Deterministic source: Returned identity fields come from the decoded barcode payload, not generative guessing.
- •Retake-safe errors: PDF417_NOT_DECODED and AAMVA_NOT_VALID return explicit 422 responses, with an optional capture_issue hint.
- •License or ID card: document_kind reports which record the barcode carries; ID cards return null license class, restrictions, and endorsements.
- •Local demand: Built for fintech and industrial-bank onboarding, ski rentals, and medical cannabis.
Illustrative Utah ID Card Response
This response uses wholly fictional data to show a UT identification card. A license returns document_kind driver_license and its class fields.
{
"success": true,
"data": {
"type": "drivers_license",
"document_kind": "id_card",
"source": "pdf417",
"country_code": "USA",
"region": "UT",
"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": null,
"restrictions": null,
"endorsements": null,
"document_discriminator": "SAMPLE-DISCRIMINATOR",
"issuer_identification_number": null,
"aamva_version": 10,
"jurisdiction_version": 0
}
}Frequently Asked Questions
Does the API read Utah state ID cards as well as driver licenses?
Yes, when the back of the card carries a usable AAMVA record. The response sets document_kind to id_card for identification cards and driver_license for licenses.
Does a successful Utah decode prove the card is genuine?
No. It proves a usable barcode payload was decoded and parsed. Authenticity, identity, eligibility, and fraud decisions require separate controls.
What should the app do after a 422 response?
Ask for a new photo of the full Utah card back in even light, using the capture_issue hint when present. Do not fill missing fields from an uncertain barcode.
You May Also Like
Related tutorials, platform guides, and comparisons
North Carolina Driver License OCR: Extract Fields with Python
Extract visible fields from North Carolina driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
New Zealand Driver License OCR: Extract Fields with Python
Extract visible fields from New Zealand driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Nebraska Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Nebraska driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
Texas Driver License PDF417 API
Decode the PDF417 barcode on the back of a Texas driver license or State ID and return normalized AAMVA fields as structured JSON.
Michigan Driver License PDF417 API
Decode the PDF417 barcode on the back of a Michigan driver license or State ID and return normalized AAMVA fields as structured JSON.
Vermont Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Vermont driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
US Driver License OCR with Python SDK
Extract structured fields from a United States state-issued driver license with the StructOCR Python SDK and FastAPI.
UK Driver License OCR with Node.js SDK
Extract structured fields from a United Kingdom photocard driving licence with the StructOCR Node.js SDK and TypeScript + Express.
US Driver License OCR with Node.js SDK
Extract structured fields from a United States state-issued driver license with the StructOCR Node.js SDK and TypeScript + Express.
UK Driver License OCR with Python SDK
Extract structured fields from a United Kingdom photocard driving licence with the StructOCR Python SDK and FastAPI.
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.
Add Passport OCR to Your Replit App in 5 Minutes
Step-by-step guide to integrating the StructOCR Passport scanner API into a Replit application. Build travel, hospitality, and global KYC flows using Replit Agent and Secrets.
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.