LogicOCR
IDENTITY & DOCUMENT OCR API

From ID to JSON.
Ready for
your app.

Turn identity cards and passport photo pages into structured data. Less typing at the desk. More time for the person in front of it.

Try the demo Explore the API
US & Canadian IDs TD3 passports
THE DOCUMENT → DATA CONNECTION 01 / 03
One document. Useful details.
IDENTITY CARDSAMPLE
SURNAMEPARKERGIVEN NAMESJAMIE ALEX
DOCUMENT NO.DEMO-0001DATE OF BIRTH14 JUL 1992
FICTIONAL DATA · NOT A VALID ID
Structured outputapplication/json
{
  "first_name": "JAMIE",
  "last_name": "PARKER",
  "date_of_birth": "1992-07-14"
}
ILLUSTRATIVE FIELDS · FICTIONAL SAMPLE
A clear format for the workflow you already have.
MADE FOR THE MOMENTS
THAT SHOULD FEEL SIMPLEGuest check-inCustomer onboardingDocument intakeDeveloper workflows
THE DETAILS, TAKEN CARE OF

Your documents.
A common language.

Bring visual text, barcode data, and passport MRZ into your application through a focused API.

01

Identity cards, decoded.

Read US and Canadian driver’s licenses and state or provincial IDs. Extract visual fields and supported AAMVA barcode data.

US / CANADA ↗
02

Passports, made readable.

Extract names, document numbers, and dates from two-line TD3 passport MRZs on deployments with passport support enabled.

ICAO TD3 MRZ ↗
03

Differences, brought to light.

Optional front-to-barcode comparisons surface mismatched fields for review. A consistency check, with clear signals for your workflow.

PDF417 + VISUAL OCR ↗
Authenticated requests. Per-client improvement controls. Document and face images returned when available.
LESS EXPLAINING. MORE EXPLORING.

See what comes back.

Explore a fictional sample, or verify your email to try your own document with 2 free image credits.

IDENTITY CARDSAMPLE
SURNAMEPARKERGIVEN NAMESJAMIE ALEX
DOCUMENT NO.DEMO-0001DATE OF BIRTH14 JUL 1992

An example, not a live scan.
Fictional data illustrates selected response fields. Use “Your document” for an actual API request.

Sample response
POST /scanIllustrative · selected fields
Switch samples to explore the response.

      

      
    

  


  

    
BUILT TO FIT YOUR STACK
One endpoint.
Every supported document.
Send one or two file uploads or a base64 array. Both input formats return the same structured JSON for your application.
Open API reference 

    
terminal
 Keep your API key in an environment variable.

    
Predictable requests
Repeat the images form field for file uploads, or send a JSON images array containing one or two base64 strings. One credit per image; invalid images are rejected before charging.
Explicit outcomes
Check status for the scan outcome and read the selected fields from data. Check that the fields your application needs are present before using the result.
Actionable errors
401 invalid key · 402 insufficient credits · 403 disabled key · 413 input too large · 415 unsupported Content-Type · 422 invalid request.

  


  

    
A FEW GOOD QUESTIONS
Before you connect.
Something else on your mind?
We’re an email away ↗

    
Which documents can I scan?+
LogicOCR supports US and Canadian driver’s licenses and identity cards, plus two-line ICAO TD3 passport photo pages. Support depends on the document format and image quality. Other MRZ formats and document families are outside the current scope. Passport availability is controlled by the deployment’s settings.
Does a matching barcode prove an ID is genuine?+
No. Front-to-barcode comparison checks whether extracted fields agree. MRZ check digits check data consistency. Neither establishes document authenticity or replaces issuer verification, liveness checks, or your review process.
How are my scans and credits handled?+
Live scans use your account’s existing settings. One uploaded image uses one credit; a two-image request uses two. Improvement capture is controlled per client. Retention and image storage depend on the deployment and account setup; contact us to confirm the right configuration.
What should I expect from scan speed?+
Processing time varies with image quality, orientation, document type, fallback reads, and server load. The API returns execution timing with each scan. Use your own representative documents to evaluate latency for your application.
How do I get API access?+
Email support@logicocr.com with your use case, document types, and expected monthly volume. We’ll help you get an account and discuss credits and pricing. Existing customers can sign in to the customer portal.

  


  
YOUR NEXT INTEGRATION STARTS HERE
Let’s take the typing
out of your workflow.
Tell us what you’re building, the documents you need to scan, and your expected volume. We’ll talk access and pricing.
Get API access support@logicocr.com ↗