Extracts structured details from an invoice or utility bill (buyer and vendor blocks with address/GSTIN/PAN, invoice details, line items and totals) from an uploaded image or PDF, using an in-region in-house OCR pipeline. Multi-page documents up to 10 pages are supported.
Document type gate: the response always carries document_type. Only TAX_INVOICE and UTILITY_BILL are accepted for address verification; a document recognised as something else (for example DELIVERY_CHALLAN, RENT_AGREEMENT or BANK_STATEMENT) returns HTTP 200 with error_code: IDTO_202 and a message naming the detected type.
Response contract: A successful extraction returns HTTP 200 with status: "success", error_code: null and a populated data object. A valid upload with nothing readable, or a document type that is not accepted, ALSO returns HTTP 200 with status: "success" but a non-null error_code (IDTO_202) and data: null - every 2xx response is status: "success", so branch on error_code, not on status. Only a raised error returns status: "error". An unreadable or oversized document returns HTTP 413 (IDTO_503); a corrupt, encrypted or over-length document returns HTTP 400 (IDTO_001). Authenticate with your X-Client-ID and X-API-KEY headers.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
401Missing or invalid authentication credentials (X-Client-ID / X-API-KEY).
429Too many requests, rate limited (IDTO_006). Retry after a short wait.
