Ontario Driver’s Licence & ID Card PDF417 API
Decode AAMVA PDF417 barcodes on Ontario driver’s licences and photo ID cards into JSON with ISO dates, postal codes, and document_kind.
Capturing Ontario Card Data Without Guesswork
Businesses in Ontario handle Toronto-area fintech onboarding, cannabis retail, and car rental. Canadian AAMVA records use year-first dates, six-character postal codes, and the CAN country code, so a parser tuned only to US samples can store wrong values without any visible error.
Normalized Output for Ontario Cards
Ontario licences and photo ID cards are issued by ServiceOntario (Ontario Ministry of Transportation). When the back of a card carries an AAMVA-compliant PDF417 barcode, the StructOCR PDF417 API decodes it, normalizes dates to YYYY-MM-DD, reports the province in region, and returns document_kind. Barcode layouts differ by card generation; cards without an AAMVA barcode return a clear 422 error, and their printed front can be read with the Driver License OCR API.
Where This Workflow Fits
- Customer onboarding: Pre-fill name, date of birth, and address for Ontario customers and confirm before saving.
- Age-restricted sales: Read date of birth from licences and photo ID cards at liquor and cannabis counters.
- Licence-only checks: Use document_kind to require a driver’s licence for vehicle rental while accepting ID cards elsewhere.
Decode a Ontario Card Back
Upload a JPG, PNG, or WebP image of the full card back and check country_code, region, and document_kind in the response.
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=@ontario-card-back.jpg"Technical Specs
- •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417 (same endpoint for US and Canadian cards)
- •Document scope: Ontario cards whose back carries an AAMVA-compliant 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: country_code CAN and region ON when encoded in the record
- •Important: Parsing barcode data does not by itself authenticate the credential or the person presenting it
Key Features
- •Date normalization: Year-first and month-first AAMVA dates both return as YYYY-MM-DD.
- •License or ID card: document_kind tells a driver’s licence from a photo ID card.
- •Deterministic source: Fields come from the decoded barcode, never from a generative model.
- •Retake-safe errors: Unreadable or non-AAMVA barcodes return explicit 422 responses for a retake or manual review path.
Illustrative Ontario Response
This response uses wholly fictional data. Available optional elements depend on what the issuer encodes.
{
"success": true,
"data": {
"type": "drivers_license",
"document_kind": "id_card",
"source": "pdf417",
"country_code": "CAN",
"region": "ON",
"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": "A1A 1A1",
"vehicle_class": null,
"restrictions": null,
"endorsements": null,
"document_discriminator": "SAMPLE-DISCRIMINATOR",
"issuer_identification_number": null,
"aamva_version": 10,
"jurisdiction_version": 0
}
}Frequently Asked Questions
Do all Ontario cards have a PDF417 barcode?
Not necessarily. Barcode use varies by card type and generation. The API supports cards with an AAMVA-compliant PDF417 record and returns a 422 error for others, so your flow can fall back to front-side OCR or manual review.
How are Canadian dates and postal codes returned?
Dates are normalized to YYYY-MM-DD and postal codes are returned as encoded, for example in the A1A 1A1 format.
Does a successful decode verify the cardholder?
No. It proves a usable barcode payload was decoded and parsed. Identity, authenticity, and eligibility decisions require separate controls.
You May Also Like
Related tutorials, platform guides, and comparisons
Oregon Driver License OCR: Extract Fields with Python
Extract visible fields from Oregon driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.
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.
Pennsylvania Driver License PDF417 API
Decode the PDF417 barcode on the back of a Pennsylvania driver license or State ID and return normalized AAMVA fields as structured JSON.
South Carolina Driver License & ID Card PDF417 API
Decode the PDF417 barcode on South Carolina driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
C# Driver's License OCR API
Upload an image for a free test! High-accuracy C# Driver's License OCR API. Get structured JSON output from images, parse PDF417 barcodes, and eliminate manual entry errors.
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.
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 Node.js SDK
Extract structured fields from a Canada provincial driver licence with the StructOCR Node.js SDK and TypeScript + Express.
Canada Driver License OCR with Python SDK
Extract structured fields from a Canada provincial driver licence with the StructOCR Python SDK and FastAPI.
Oregon Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Oregon driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
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.
VIN Barcode Scanner vs. VIN OCR API: Which is Better for Mobile Apps?
Deciding between local VIN barcode scanners and cloud-based VIN OCR API for your mobile app? Learn why OCR is the required fallback for damaged or chassis-stamped VINs.
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.