LogicOCR
ID & PASSPORT SCANNING API FOR HOTEL PMS

Guest ID to PMS-ready data.
In one API.

Scan supported guest IDs and passport photo pages, extract structured details, and send clean JSON into your hotel PMS check-in workflow—without retyping every field.

Try the demo For PMS teams
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.
BUILT FOR FAST
DATA CAPTUREHotel PMS check-inGuest registrationCustomer onboardingDocument intake
FOR HOTEL PMS & HOSPITALITY SOFTWARE

Make guest check-in
less manual.

LogicOCR gives PMS teams a focused document-data layer: capture a supported ID or passport photo page, receive structured fields, validate what your workflow needs, and map the result into the guest profile.

01Capture

Front desk or guest submits a supported ID or passport photo page.

02Extract

LogicOCR reads supported visual, barcode, or MRZ data and returns structured JSON.

03Map

Your PMS maps required fields such as name, birth date, document number, and dates.

04Review & check in

Staff reviews the returned details before continuing the property’s normal check-in process.

For PMS product teams

Add document capture without building and maintaining a complete OCR pipeline inside your PMS. Use the API as a component in your existing guest workflow.

See the API approach ↗

For hotel operations

Reduce repetitive transcription at the desk and give staff structured data they can review instead of starting from a blank guest profile.

Explore a sample ↗

Integration-friendly

Use multipart file uploads or base64 JSON and receive a predictable JSON response that your application can map to its own guest fields.

Read API reference ↗
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.
Does LogicOCR store guest ID or passport images?+
Direct scans use short-lived processing buffers. Paired phone-to-desktop delivery temporarily stores fields and enabled photos; access expires within 15 minutes, or earlier after filling or discarding. Eligible scans with no extracted text fields can also be exported to a customer’s enabled private S3 bucket, where that customer controls retention and deletion. Review the Privacy Policy for the delivery, storage and metadata details.
How can LogicOCR connect to a hotel PMS?+
Your PMS sends one or two supported document images to the LogicOCR API, receives structured JSON, validates the fields it needs, and maps those fields into its guest or reservation workflow. LogicOCR does not require the PMS to adopt a specific guest-profile schema.
Can LogicOCR determine whether an identity document is authentic?+
No. LogicOCR extracts data and can surface supported consistency signals, but it is not a substitute for document authentication, issuer verification, liveness checks, or a hotel’s review process.
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 ↗