Two different problems wear the same name. A steady flow of documents arriving daily is a throughput question. A decade of archived files is a project with an end date. They need different sizing and different code.
Talk to our technical team → — for integration questions, a security review or a volume estimate.
A batch call returns a ZIP containing the processed
documents and a manifest.json giving per-document status. The HTTP status only
tells you the batch was accepted.
X-Quota-Remaining comes back on every call. Alert at a threshold; do not discover the ceiling by hitting it.Forty thousand archived documents, a four-week window. The shape of the plan matters more than the numbers.
scan.pdf. Name files with your own id before sending.Set per plan. Higher-volume plans take larger batches; a negotiated plan can be sized to whatever your pipeline emits. Note that batching amortises the HTTP round trip, not the OCR work — fifty documents is fifty documents of processing either way.
The rest are still processed and returned. That document gets a failed status in the manifest.
Yes for /bulk/anonymise, which is document-agnostic. The Aadhaar and PAN batch endpoints expect their own document type.
Sample a few hundred documents first. That gives you a real processing rate and, more importantly, the proportion that come back with nothing found — which is the share needing human attention and usually the part that determines the timeline.
Counting no-number findings as successes. Those documents were returned unchanged and are still fully readable, so a run reporting 40,000 processed can leave thousands of readable documents in the archive while the report says the project is done.
Tell us how many documents a month you process and what your peak looks like. We will size a plan, provision a key with a test quota, and answer a security questionnaire if you need one.