Proof of Delivery OCR API

4.8/5

(30+ reviews)

Proof of delivery OCR API that reads every POD, signed or stamped

Turn signed delivery receipts and carrier PODs, scans or driver photos, into structured JSON. Delivery date, receiver, signature, packages and exceptions, each with a confidence score.

No credit card required

SOC 2 Type II & GDPR

Proof of delivery OCR API reading POD number, receiver, signature and delivery remarks from a signed receipt into JSON

Trusted by finance and product teams at

Why invoices wait on paper PODs

Drivers bring back signed receipts in every format, folded, stamped and annotated. Billing teams scan, read and key each one, then match it to the order before they can invoice.

POD returned

Driver drops signed PODs at the depot.

Batch scanning

Paper sorted and scanned by the batch.

Friction

PODs get lost between truck and office.

Manual keying

Date, receiver and remarks typed in.

Friction

Exceptions stay buried in handwriting.

Order matching

POD matched to the order before billing.

Friction

Invoices wait for missing PODs.

Invoice released

Finally billed, one POD at a time.

RESULT

[X] days between delivery and invoice, and [X]% of PODs carrying an exception nobody spotted.

See how Mindee fixes it

Delivery

pod_number, delivery_date, delivery_time

Receiver

receiver_name, signature_present

Delivered to

consignee_name, delivery_address

Shipment

carrier_name, shipper_name, driver_name

References

reference_number

Packages & remarks

package_count, remarks

response.json

{

"pod_number": { "value": "RX-88412095" }, "delivery_date": { "value": "2026-10-15" }, "delivery_time": { "value": "14:32" },

"receiver_name": { "value": "M. Torres" }, "signature_present": { "value": true },

"consignee_name": { "value": "Ridgeway Plumbing Supply" }, "delivery_address": { "value": "Dock 4, 900 Industrial Pkwy, Reno, NV" },

"carrier_name": { "value": "Redline Express" }, "shipper_name": { "value": "Atlas Valve Co." }, "driver_name": { "value": "D. Kim" },

"reference_number": { "value": "PO-58213" },

"package_count": { "value": 12 }, "remarks": { "value": "1 carton crushed, contents OK" },

}

Ready to post, not just to read.

Fields come from a data schema you define in minutes. Dates come back in ISO 8601, the signature as true or false, each field with a confidence score.

Built for real PODs, not clean scans

Carbon copies, rubber stamps over the signature, remarks scribbled in the margin, photos taken on a tailgate. The model reads what the receiver wrote and flags what it is unsure of.

Proofs of delivery from six carriers flowing through Mindee into one POD schema

Any carrier, any POD format

Signed receipts, carrier PODs and driver-app printouts all look different. They come back in one schema you define, with no template per carrier.

Three PODs checked for a signature, two released for invoicing and one unsigned POD put on hold

Signatures checked before billing

signature_present comes back true or false with the printed receiver name, so unsigned PODs are caught before you invoice.

Handwritten POD remarks about damage and shortage extracted as text and routed to claims review

Exceptions flagged for claims

Handwritten remarks like "1 carton crushed" come back as text, so damage and shortages reach your claims team the same day.

POD photographed by a driver, detected and cropped from the photo, then extracted into fields

Driver photos cropped and read

Drivers photograph PODs on a tailgate. Mindee detects the page in the photo, crops it and extracts it like a clean scan.

PDF / JPEG / PNG / WEBP / TIFF / HEIC, Signed receipts & carrier PODs, Stamps & signatures, Handwritten remarks, Driver phone photos

POD OCR accuracy you can measure, field by field

Every field comes with a confidence score, so clean PODs release invoices automatically and unclear handwriting goes to a reviewer. Test it on your own PODs in the free trial.

96.4%

Field-level accuracy on printed fields

POD number, date, consignee

92.1

Accuracy on signature detection

Signed, stamped, missing

0.9s

Median time per POD

Single page, synchronous call

A confidence score on every field

Set your own threshold. Fields above it flow straight to your systems; anything below lands in a review queue, with the exact spot on the proof of delivery highlighted. Définissez votre propre seuil. Les champs au-dessus partent directement dans vos systèmes ; les autres rejoignent une file de vérification, avec leur emplacement exact mis en évidence sur votre proof of delivery.

Auto-approve the proofs of delivery you can trust Validez automatiquement les proofs of delivery fiables

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.

Prototype in minutes, go live with the API

Start with a no-code workflow to prove the value on your own proofs of delivery, then move the same model into your product. Commencez par un workflow no-code pour prouver sa valeur sur vos propres proofs of delivery, puis intégrez le même modèle dans votre produit.

What teams build with proof of delivery OCR

The same API powers very different products. Here is where it usually starts.

Rated 4.8/5 by developers and operations teams

4.8

on G2

4.9

on Capterra

quote

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.

on G2

quote

Mindee is a software that helps us to convert all of our physical business data like bills, invoices, warranty cards, calendar, recipts received to us into a digital documents that can be stored in our drive and can be uploaded in different type of Excel sheets so that all the updates can be maintained and a proper analytics of transactions can be kept by the financial team

on G2

quote

I like the easiness and how to use it. Also the price model is very fair. Good with space for improvement

on Capterra

FAQ about Mindee's Proof of Delivery OCR API

Can't find what you're looking for? Our team answers within one business day.

About proof of delivery OCR À propos de l’OCR pour les proof of delivery

What is a proof of delivery?

A proof of delivery (POD) is the document that confirms a shipment reached its destination. It is usually signed by the person who received the goods and records the delivery date and time, the receiver’s name, the delivery address, the number of packages and any remarks about damage or shortages. Carriers and shippers use it to close the shipment, send the invoice and support claims or disputes. PODs can be paper receipts signed on the spot or electronic records captured in a driver app. With Mindee, you define the POD fields you need in a data schema, and each delivery receipt, scan or driver photo comes back as structured JSON with a confidence score for every field.

What’s the difference between a delivery note, a proof of delivery and a bill of lading?

A delivery note travels with the goods and lists what is being delivered. It is issued by the seller or the shipper. Once the recipient signs it to confirm receipt, often adding remarks, it becomes a proof of delivery. A bill of lading is different: it confirms that the carrier received the goods at loading, but not that they reached the recipient. Mindee recognizes each of these documents, even when they arrive together, so each one goes to the right step of your process.

Can Mindee read handwritten remarks, signatures and stamps on PODs?

Yes. PODs are often signed on the spot, stamped, annotated by hand and photographed by drivers in poor conditions. Mindee reads both printed and handwritten content, detects whether the document is signed or stamped, and extracts handwritten remarks such as “2 cartons damaged” or corrected quantities. These remarks are the key information in a delivery dispute. PODs with reservations or unclear fields can be flagged automatically and sent to your team, while clean deliveries are processed straight away.

How does POD automation speed up invoicing and payments?

Carriers and logistics providers often can’t invoice a delivery until they have received and checked the signed POD. When thousands of PODs arrive as paper or photos, this can delay invoicing by days or weeks. With Mindee, each POD is processed as soon as it is uploaded: the shipment reference, delivery date and signature are checked automatically, and the invoice can be issued right away. On the shipper side, the POD serves as the goods receipt in three-way matching, alongside the purchase order and the invoice, so payment can be approved without manual checks.

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 PODs?

Build your POD model from a sample in minutes and send your first delivery receipt to the API, with a team of document processing engineers behind it.

14-day free trial

No credit card required