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.
Capturing Texas License-Back Barcodes Reliably
Texas workflows frequently span distributed branches and field teams, so barcode images arrive from many camera models and lighting conditions. A consistent capture contract matters more than trying to repair uncertain identity values later. PDF417 error correction can recover some damage, but an application should never invent identity values when the payload cannot be decoded.
Normalized AAMVA Data for Texas Workflows
Send the complete back image to the StructOCR PDF417 API. The service decodes the barcode deterministically, parses the record defined by the AAMVA DL/ID standard, and normalizes the jurisdiction to TX. Require a sharp image of the complete license back and show an immediate retake message for glare, motion blur, or a missing barcode row. The free PDF417 scanner can be used to test non-sensitive samples before integration.
Where This Workflow Fits
- Fleet driver intake: Pre-fill names, license number, dates, and address for fleet driver intake while keeping final confirmation in the application.
- Equipment rental prefill: Use normalized region
TXand available AAMVA fields to reduce transcription in fleet onboarding, branch-based rentals, and field-service operations. - Field-service onboarding: Send unreadable Texas barcodes to a retake or review queue instead of saving incomplete identity data.
Decode a Texas License Back
Upload a JPG, PNG, or WebP image with the full Texas PDF417 barcode visible. The SDK tabs show equivalent server-side calls.
Prerequisite: A server-side StructOCR API key and a clear image of the complete license back
curl -X POST https://api.structocr.com/v1/driver-license-pdf417 \
-H "x-api-key: $STRUCTOCR_API_KEY" \
-F "file=@texas-license-back.jpg"Technical Specs
- •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417
- •Document scope: Back of a US driver license or State ID 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: TX when encoded in a valid Texas record
- •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 produce explicit 422 responses.
- •Normalized output: Names, dates, address components, class, restrictions, and endorsements use stable JSON keys when present.
- •State routing: The normalized region field identifies Texas as TX.
Illustrative Texas AAMVA Response
This response uses wholly fictional data to demonstrate the normalized TX shape. Optional elements can be null when they are not encoded.
{
"success": true,
"data": {
"type": "drivers_license",
"source": "pdf417",
"country_code": "USA",
"region": "TX",
"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
Can the API decode a Texas State ID as well as a driver license?
Yes, when the back contains a usable AAMVA driver-license or identification-card record. The returned type and available optional elements depend on what is encoded.
Does a successful Texas PDF417 decode prove the card is genuine?
No. It proves that 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 Texas license back in even light. Do not fill missing fields from an uncertain or partially visible barcode.
You May Also Like
Related tutorials, platform guides, and comparisons
Ireland Driver License OCR: Extract Fields with Python
Extract visible fields from Ireland driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Kenya Driver License OCR: Extract Fields with Python
Extract visible fields from Kenya driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Saudi Arabia Driver License OCR: Extract Fields with Python
Extract visible fields from Saudi Arabia driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Colorado Driver License OCR: Extract Fields with Python
Extract visible fields from Colorado driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
Canada Driver License OCR with Node.js SDK
Extract structured fields from a Canada provincial driver licence with the StructOCR Node.js SDK and TypeScript + Express.
Philippines Driver License OCR with Python SDK
Extract structured fields from a Philippines LTO driver's license with the StructOCR Python SDK and FastAPI.
Canada Driver License OCR with Python SDK
Extract structured fields from a Canada provincial driver licence with the StructOCR Python SDK and FastAPI.
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.
Philippines Driver License OCR with Node.js SDK
Extract structured fields from a Philippines LTO driver's license with the StructOCR Node.js SDK and TypeScript + Express.
VIN Barcode Scanner vs. VIN OCR: Which is Better?
Deciding between a VIN barcode scanner and VIN OCR for your mobile app? Learn why OCR is the only reliable solution for damaged, glaring, or chassis-stamped VINs.
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.
AWS Textract & Google Vision vs. StructOCR Passport API
How AWS Textract AnalyzeID, Google Cloud Vision OCR, and the StructOCR Passport API differ for passport data, quoting each vendor’s own documentation.
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.