Newfoundland and Labrador Driver’s Licence & ID Card PDF417 API
Decode AAMVA PDF417 barcodes on Newfoundland and Labrador driver’s licences and photo ID cards into JSON with ISO dates, postal codes, and document_kind.
Capturing Newfoundland and Labrador Card Data Without Guesswork
Businesses in Newfoundland and Labrador handle offshore energy crews, tourism rentals, and rural healthcare. 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 Newfoundland and Labrador Cards
Newfoundland and Labrador licences and photo ID cards are issued by Motor Registration Division, Digital Government and Service NL. 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 Newfoundland and Labrador 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 Newfoundland and Labrador 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=@newfoundland-and-labrador-card-back.jpg"Technical Specs
- •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417 (same endpoint for US and Canadian cards)
- •Document scope: Newfoundland and Labrador 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 NL 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 Newfoundland and Labrador 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": "NL",
"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 Newfoundland and Labrador 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
Kansas Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Kansas driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
Why Cropped Driver License PDF417 Barcodes Fail
Prevent cropped PDF417 failures by preserving barcode quiet zones, complete stacked rows, image orientation, and enough surrounding card context.
Philippines Driver License OCR with Python SDK
Extract structured fields from a Philippines LTO driver's license with the StructOCR Python SDK and FastAPI.
Washington Driver License & ID Card PDF417 API
Decode the PDF417 barcode on Washington driver licenses and state ID cards into AAMVA JSON, with document_kind to tell licenses from ID cards.
UK Driver License OCR with Python SDK
Extract structured fields from a United Kingdom photocard driving licence with the StructOCR Python SDK and FastAPI.
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 Python SDK
Extract structured fields from a Brazil Carteira Nacional de Habilitação (CNH) with the StructOCR Python SDK and FastAPI.
Next.js Route Handler PDF417 Driver License API
Build a Next.js server route that decodes US driver license PDF417 barcodes and returns normalized AAMVA JSON with safe retake handling.
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.
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.