Insurance Card OCR API
4.8/5
(30+ reviews)
Insurance card OCR API that reads any US health insurance card
Turn a phone photo or scan of a member's card into structured JSON in seconds. Member ID, group number, payer ID, Rx BIN and PCN, copays and dependents, with a confidence score on each value.
No credit card required
SOC 2 Type II & GDPR

Trusted by finance and product teams at




Why insurance card data slows down intake
Every payer prints its own layout, with member ID, group number and Rx codes in different places, front and back. Staff retype each card, and one wrong digit fails the eligibility check.
Card received
Photo from a patient portal or a front desk scan.
Manual keying
Member ID, group and Rx codes typed into the PMS.
Friction
Long IDs and look-alike codes invite typos.
Eligibility check
Coverage verified with the payer before the visit.
Friction
One wrong digit and the check comes back empty.
Claim rework
Denied claims sent back to be corrected.
Friction
Denials land weeks after the visit.
Record updated
Finally in the system, one card at a time.
Every insurance card field you need, as structured JSON
Hover a group to see where it lands in the response. Every value comes back typed, normalised and located on the card.
See fields list
Plan
company_name, plan_name, issuer_80840
Member
member_name, member_id, enrollment_date
Group & payer
group_number, payer_id
Pharmacy (Rx)
rx_bin, rx_pcn, rx_grp, rx_id
Copayments
copayments[].service_name, copayments[].service_fees
Dependents
dependents
{
"company_name": { "value": "Blue Harbor Health" }, "plan_name": { "value": "Choice PPO Gold" }, "issuer_80840": { "value": "80840 9140461006" },
"member_name": { "value": "Jordan Carter" }, "member_id": { "value": "BHX928374651" }, "enrollment_date": { "value": "2026-01-01" },
"group_number": { "value": "GRP-0047210" }, "payer_id": { "value": "60054" },
"rx_bin": { "value": "610014" }, "rx_pcn": { "value": "MEDDPRIME" }, "rx_grp": { "value": "RX4521" }, "rx_id": { "value": "BHX928374651" },
"copayments": [ { "service_name": { "value": "primary_care" }, "service_fees": [ { "value": 25 } ] }, { "service_name": { "value": "emergency_room" }, "service_fees": [ { "value": 250 } ] } ],
"dependents": [ { "value": "Emma Carter" }, { "value": "Noah Carter" } ],
}
Ready to post, not just to read.
Dates come back in ISO 8601, copays as numbers, and every field carries a confidence score and its position on the card.
Built for cards in a patient's hand, not on a flatbed
Phone photos taken at the front desk, glare on a laminated card, front and back in one upload. The model was trained on the cards patients actually carry.

Any payer, one schema
National carriers, regional plans, employer cards: the same JSON comes back whatever the layout, with no template to build per payer.

Front and back in one upload
Member data on the front, pharmacy codes on the back. Send both sides as one file and get a single result for the card.

Copays returned as data
Primary care, specialist, urgent care and ER copays come back as a list of services with their fees, ready for cost estimates.

ID and insurance card on one scan
Front desks often copy the photo ID and the insurance card on one page. Each card is found, classified and read by the right model.
PDF / JPEG / PNG / WEBP / TIFF / HEIC, Front & back in one upload, Any payer layout, Phone photos & scans, ID & insurance card on one scan
Insurance card OCR accuracy you can measure, field by field
Measured on real member cards, not curated samples. Run the same benchmark on your own cards during the free trial.
96.6%
Field-level accuracy on member fields
Member ID, group, payer
93.8%
Accuracy on pharmacy fields
Rx BIN, PCN, group, ID
0.8s
Median time per card
Front and back, synchronous call
A confidence score on every field
Send only real exceptions to a human

Document AI features, better than OCR
Prepare, classify and extract. Mindee delivers high-accuracy extraction for every document format, so you can automate workflows with speed and high reliability.
Data extractor
Classifier
Splitter
Edge detector
Pull the exact fields you need from any document
Pick a ready-made model or describe your own data schema. Every value comes back typed, normalised, located on the page and scored.
- Prebuilt models or your own custom schema
- Tables and line items, across pages
Know what each document is before you read it
The classifier labels every upload with your own classes, so an ID card goes to onboarding and an invoice goes to accounts payable.
- Your own document classes
- Route each type to the right model
One scanned batch in, separate documents out
Send a long PDF from the office scanner. Mindee finds where each document starts and ends, and returns them one by one.
- Page ranges for every detected document
- Up to 200 pages and 100 MB per file
Several documents on one photo? Each gets its own crop
Users photograph three receipts on a desk, or both sides of an ID. Mindee detects each border, returns its coordinates and reads them separately.
- Coordinates for every detected document
- Built for mobile capture flows
Prototype in minutes, go live with the API
Step 1 : Prototype
Run a proof of concept in Make, Zapier or n8n
No code, no IT ticket. Point a mailbox at Mindee and watch the data arrive in a spreadsheet.
Card photo uploaded
Patient portal or front desk
Mindee extracts the card
Member, plan, Rx, copays
Patient record updated
Your EHR, PMS or Google Sheets
Low-confidence fields sent for review
Slack or email alert to your team
Step 2 : Production
Integrate the API into your platform
Official SDKs, typed responses and webhooks for async processing. Most teams ship the integration in a day.
mindee docs
$ pip install mindee
Your app
Mindee API
Your ERP/CRM
.webp)
Integrate Mindee into your workflow in minutes with SDKs & no-code tools
Go live in minutes using our verified Zapier & Make.com app with zero coding, or integrate seamlessly via our well-documented REST API built for developers. SDKs available for Python, .NET, Node.JS, Java, Ruby, PHP.
Integrations

Enterprise-grade security
Our API has a SOC 2 Type II certified infrastructure and is GDPR Compliant to ensure your file information remains protected at all times.
EU or US hosting available
GDPR, CCPA Compliant
Security center
What teams build with insurance card OCR
The same API powers very different products. Here is where it usually starts.

Insurance
Claim management
Read every claim attachment, settle simple claims and route the rest to the right adjuster.

Banking & lending
Insurance
Customer onboarding
Read and cross-check every onboarding document, from ID to bank details, in real time.

Banking & lending
Real estate
Loan requests
Turn payslips, bank statements and tax returns into decision-ready data for underwriting.
Rated 4.8/5 by developers and operations teams
4.8
4.9
Mindee works reliably and delivers good performance. The OCR data is accurate, and the API is stable. It works like a charm.
Mindee works reliably and delivers good performance. The OCR data is accurate, and the API is stable. It works like a charm.
Mindee is a web based tool that help us in scanning and reading different type of documents like identity cards, invoices, proposal plans etc and extract all the information with its AI and then it provides all the information and data associated with these documents a structured way.
Mindee is an integrated document processing platform backed by reliable AI technology. The service has an intuitive and user-friendly interface and provides highly accurate results extracting data from various document types, especially financial receipts and invoices, which are relatively complex for efficient data extraction and automation.
FAQ about Mindee's Insurance Card OCR API
Can't find what you're looking for? Our team answers within one business day.
How do you read a US health insurance card?
A US health insurance card usually shows the insurer’s name and plan type (HMO, PPO, EPO…), the member’s name and member ID, the group number, and the copays for common visits. Prescription details (Rx BIN, Rx PCN and Rx Group) are used by pharmacies, and the back often lists the payer ID, the claims address and customer service phone numbers. Mindee extracts all these fields from a photo of the front and back of the card and returns them as structured JSON. Healthcare providers can then fill in patient records and insurance information without manual typing.
What’s the difference between the member ID, policy number and group number?
The member ID (sometimes called the policy number or subscriber ID) identifies the individual covered by the plan. Dependents often share the subscriber’s ID, with a different suffix. The group number identifies the plan the member belongs to, usually through their employer. Both are needed for eligibility checks and claims, and mixing them up is a common source of errors at patient intake. Mindee returns each one as a separate, clearly labeled field, whatever the insurer’s wording or card layout.
Does Mindee work with cards from every insurer?
Yes. Every insurer uses its own card design and terminology, whether it’s Aetna, Blue Cross Blue Shield, Anthem, Cigna, UnitedHealthcare, or Medicaid and Medicare Advantage plans. Mindee doesn’t rely on templates, so it handles these different layouts and returns the same output structure for every card. Patients can simply take a photo of their card on their phone during online check-in, and your team receives data that is ready for eligibility verification. This reduces front-desk work and helps prevent claim denials caused by incorrect insurance information.
Is Mindee HIPAA compliant?
Health insurance cards contain protected health information (PHI), so how it is processed matters. Mindee could be HIPAA compliant and can sign a Business Associate Agreement (BAA) with covered entities and business associates. It is mainly focused on SOC 2 Type II certified, and data is encrypted in transit and at rest. You stay in control of data retention, so you can keep only the fields you need in your own systems.
About Mindee
Is my data secured and protected during the conversion process?
Yes, your data is highly secured and protected during the entire conversion process. As an enterprise-grade OCR solution, Mindee takes data privacy very seriously. Here are the key security measures in place:
- Certified compliance: Mindee's infrastructure is SOC 2 Type II certified and fully GDPR compliant, ensuring strict industry standards for data protection.
- Encryption: All documents and extracted data are fully encrypted both in transit (during the API call) and at rest.
- Data localization: You have control over where your data is processed, with the option to host and process your data on either EU or US servers.
- Strict privacy: Mindee respects data confidentiality. Your processed documents are not shared with third parties, and your private data is not used to train global AI models.
In short, your sensitive documents are processed in a secure, isolated environment and remain completely under your control.
Is Mindee's OCR API free to use?
We provide a 14 days free trial so you can fully test any of our OCR models — no credit card required. After this, we offer different pricing tiers depending of the volume of pages processed and the features you might need. See the pricing page for more information.
What file formats are supported for JSON conversion?
The supported document formats are:
- PDF (
application/pdf) – While technically a document format rather than an image, it is natively supported for all extraction models. - JPEG / JPG (
image/jpeg) - PNG (
image/png) – Must be non-animated. - WebP (
image/webp) - TIFF / TIF (
image/tiff) – Both single-page and multi-page TIFFs are supported and processed similarly to PDFs. - HEIC (
image/heic) – Apple's High-Efficiency Image Container format.
📌 Important technical limitations to keep in mind:
To ensure the OCR pipeline runs smoothly and successfully returns your JSON, make sure your files adhere to the following constraints:
- Maximum file size: 100 MB per file.
- Maximum page count: Up to 200 pages per document.
- File state: The files cannot be encrypted, and PDFs must not be password-protected.
Ready to stop keying insurance cards at intake?
Send your first card to the API in minutes, with a full team of engineers dedicated to document processing behind it.
14-day free trial
No credit card required